Bug 1011275 - Anchor links in DocBuilder URL don't work the first time a page is opened in Firefox
Summary: Anchor links in DocBuilder URL don't work the first time a page is opened in ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1013825
TreeView+ depends on / blocked
 
Reported: 2013-09-24 01:26 UTC by Matthew Casperson
Modified: 2014-08-04 22:27 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-02 02:43:18 UTC
Embargoed:

Attachments (Terms of Use)

Description Matthew Casperson 2013-09-24 01:26:42 UTC 
Open the link http://docbuilder.usersys.redhat.com/13968/#About_This_Guide in Firefox (tested on Firefox 17 and 24), and the first time the browser will not stay at the top of the page. The second time the link is entered, the browser will scroll down to the correct position.

Chrome works OK.
Comment 1 Matthew Casperson 2013-09-24 01:27:22 UTC 
This seems to happen with all anchors in DocBuilder pages.
Comment 2 Matthew Casperson 2013-09-24 01:33:33 UTC 
Building the book with Publican and jumping to anchors works OK.
Comment 3 Misty Stanley-Jones 2013-09-26 01:58:01 UTC 
I feel silly because I've noticed this for quite some time but thought "It must just be me"
Comment 4 Matthew Casperson 2013-10-02 01:54:50 UTC 
Including jquery (even without any other scripts) causes this.
Comment 5 Matthew Casperson 2013-10-02 02:43:18 UTC 
I'm not exactly sure what is causing this, but moving the jQuery script to the end of the HTML page instead of in the head fixes the issue.

There is no real downside to having the page load before the scripts (and all the scripts run after the DOM is ready anyway).

Any newly built specs will have the change enabled, and all books will pick it up with the next full rebuild.
Note You need to log in before you can comment on or make changes to this bug.