Closed
Bug 1201931
Opened 10 years ago
Closed 10 years ago
When a link to a page includes a anchor, and destination page also has an ajax form the page infinitely reloads.
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: troubleshooting8, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150826023504
Steps to reproduce:
I navigated to a page using a url that included an anchor. The destination page had standard content and an ajax form. example http://not_real_site.com/about-mrc/firefoxhuh#madrid
Actual results:
When the page loaded, it went into an infinite loop and restarted the page load continuously.
Expected results:
The page would load and jump down to the anchor
Reporter | ||
Updated•10 years ago
|
Summary: When a link to a page includes a jumplink, and destination page also has an ajax form the page infinitely reloads. → When a link to a page includes a anchor, and destination page also has an ajax form the page infinitely reloads.
Reporter | ||
Comment 1•10 years ago
|
||
Unfortunately, I cannot disclose a sample url since this project has not launched yet.
![]() |
||
Comment 2•10 years ago
|
||
This works in general, so there's something specific the scripts on that page are doing that's causing a problem. If you're not able to provide a link, are you able to attach the relevant HTML and scripts to this bug report? As things stand, there's unfortunately nothing to work with here. :(
Flags: needinfo?(troubleshooting8)
Reporter | ||
Comment 3•10 years ago
|
||
During debugging I came across this post:
http://stackoverflow.com/questions/7110023/firefox-6-infinite-page-refresh-with-page-with-hash-tags
Updating the MicrosoftAjax.js and debug files fixed this issue.
![]() |
||
Comment 4•10 years ago
|
||
Thank you for digging into that! Looks like the old script sniffed for Firefox and purposefully reloaded the page. :(
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(troubleshooting8)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•