Open Bug 1287514 Opened 9 years ago Updated 3 years ago

Nightly does not jump to html ID bookmarks upon tab/page load (page.html#bookmarkID)

Categories

(Core :: Layout, defect)

29 Branch
Unspecified
Windows 10
defect

Tracking

()

Tracking Status
firefox47 --- wontfix
firefox48 --- wontfix
firefox49 --- wontfix
firefox-esr45 --- affected
firefox50 --- wontfix
firefox51 --- fix-optional

People

(Reporter: sean.camanyag, Unassigned)

References

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0 Build ID: 20160718030454 Steps to reproduce: Load a page (nightly safe mode) with a #ID bookmark in the URL, both clicking the link and by opening a new tab and pasting the URL: http://us.battle.net/forums/en/overwatch/topic/20747074790#post-5 Actual results: The page loads but stays at the beginning of the page content. Expected results: The page should load then jump to the #post-5 ID, placing the 5th post of the forum thread at the top of the page window.
After page load, if you then click in the address bar and hit enter, Nightly will then jump to the bookmark.
Regression window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=6e5d4c425fcc&tochange=95f43cea056e regressed by: c64703059abd Neil Rashbrook — Bug 952087 Anchor scroll fails if the anchor is created between DOMContentLoaded and onload r=smaug
Blocks: 952087
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
OS: Unspecified → Windows 10
Component: Untriaged → Layout: Misc Code
Product: Firefox → Core
Version: 50 Branch → Trunk
Version: Trunk → 29 Branch
Jet, this is broken in fx, works in chrome.
Flags: needinfo?(bugs)
Bug 952087 landed to fix a similar issue on msdn.microsoft.com. We should avoid regressing that fix from FF29 and, like bug 952087, this one seems timing-related (see comment 1.)
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.