Closed Bug 773729 Opened 13 years ago Closed 13 years ago

Firefox will not jump to named anchor links on first page load

Categories

(Firefox :: General, defect)

13 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 668213

People

(Reporter: firstpeterfourten, Unassigned)

References

()

Details

(Whiteboard: DUPME)

Visiting a page with a named anchor/element ID link, Firefox does not always jump to that point in the page, when first loaded; it instead loads scrolled to the bottom of the page. Putting the cursor in the address bar and pressing Enter causes Firefox to jump to the desired element, though pressing Refresh does not (or at least not always) cause the desired jump. Hitting refresh also does not cause FF to go to the bottom of the page, where it initially loaded. I've looked at random first-Talk-Page-discussion links on Wikipedia and found that this can be pretty clearly seen at: https://en.wikipedia.org/wiki/Talk:Autism#RBS-R_check_needed but NOT at: https://en.wikipedia.org/wiki/Talk:Firefox#Update_64-bit_section though I cannot figure out why it should work on one of these discussions and not the other. (Let's keep the discussion limited to technical differences in the code.) Both of the URLs display the expected behavior in Google Chrome. I also checked and the id does not contain whitespace at the end, so this isn't Bug 517540. Any ideas why FF isn't jumping to the right place on the page until you press enter in the address bar?
Version: 11 Branch → 13 Branch
this is a duplicate
Whiteboard: DUPME
as I suspected it might be, but I couldn't find what it's a duplicate of. 517540 is pretty close, but there's a different trigger. If anybody finds what it's a duplicate of, indicate that...but I think the effort might be better spent searching for a solution.
> 517540 is pretty close no, I think of bug 668213, bug 633821
Yeah, that's it. I'm definitely not impressed to see unaddressed regressions in core functionality like loading a named anchor, especially with no desire to fix the issue..."just use another browser" is a proposed and viable solution, and where this bug affects externally loaded links that means the workaround is changing the system default browser. I'm sad to see and to make this recommendation. Maybe it'll eventually be working again!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.