User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:188.8.131.52) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:184.108.40.206) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) When Firefox is started, if the home page is set to a page that uses a named anchor for positioning, Firefox will ignore the anchor position and instead display the top of the page. If you click refresh, the page will reload and position itself at the named anchor as it is supposed to. This bug was not there in the 3.0.X version of Firefox, and just began when I upgraded to 3.5.1 Reproducible: Always Steps to Reproduce: Set the home page to a URL with a named anchor Exit Firefox Restart Firefox (The top of the home page displays as if the named anchor doesn't exist) Click refresh (The page reloads at the position of the named anchor) Actual Results: See the details above. Expected Results: See the details above
Here's another example (I think) of this problem: http://www.baseball-reference.com/players/split.cgi?n1=weaveje02&year=Career&t=p#hmvis The URL provided has an anchor (A) tag with the name "hmvis" enclosing an H4 pair. Firefox renders this by moving the page under the H4; you would expect it to start where the H4 starts.
I'm using 3.0.11 on Linux, incidentally.
Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.
Whiteboard: [CLOSEME 2011-1-1]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
Sorry, somehow your reply of 2010-12-03 got eaten. Yes, this problem still exists. Using 3.6.13 on MacOS 10.6.5.
You need to log in before you can comment on or make changes to this bug.