Bug Tracker

Opened 13 years ago

Closed 13 years ago

Last modified 11 years ago

#5034 closed bug (invalid)

Jquery history problem at IE7 after refresh's click of toolbar

Reported by: soniad Owned by:
Priority: major Milestone: 1.4
Component: unfiled Version: 1.3.2
Keywords: history problem at IE7 after refresh Cc: [email protected]
Blocked by: Blocking:


As per our architecture's requirement we need multiple user controls to be loaded into same aspx page through Ajax requests.So we are maintaining the history with Jquery.history.js.Things are working fine with back and forward buttons.But If we press refresh of browser toolbar then history of that page is lost (Means of multiple Ajax requests).This problem is coming in IE7 .Its working fine in mozrilla and IE8.I am attaching one prototype project also in which we are trying the same.Please set HistoryPage2.aspx as start page to test the application.On this page on click of different links we are loading contents through Ajax.History is also being managed through a hash value in URL.But if we click on refresh button at HistoryPage2.aspx its back and forward are disabled now.Please let us know if anything we are missing or any pulgin we need for same.

Attachments (1)

HistoryPage2.aspx (4.8 KB) - added by soniad 13 years ago.

Download all attachments as: .zip

Change History (4)

Changed 13 years ago by soniad

Attachment: HistoryPage2.aspx added

comment:1 Changed 13 years ago by soniad

Not able to upload whole application because of size limit uploading only HistoryPage2.aspx.That may provide an idea what we are implementing.

comment:2 Changed 13 years ago by dmethvin

Resolution: invalid
Status: newclosed

There are too many things at play here to file a bug against jQuery core. You'll need to create a simple test case that doesn't include any server side code.

comment:3 Changed 12 years ago by anonymous

I am experiencing the same issue in IE7. The hash is getting double encoded on the back button.

hash on the first call is #searchid=&type=lot&search=REAL&sort=relevance&length=10&start=1&refine=

The user clicks on a refinement and then uses the back button

pressing the back button the hash should be the same as before but now looks like this: "searchid%3D%26type%3Dlot%26search%3DREAL%26sort%3Drelevance%26length%3D10%26start%3D1%26refine%3D&1289924283501"

equals and ampersands are encoded - this does not occur in all the current browsers. Unfortunately we still have to support IE7.

Note: See TracTickets for help on using tickets.