56287 - if reload page with named-anchor URL, page displays at top, not at anchor point

Status: VERIFIED DUPLICATE of bug 56285

(Core :: Layout, defect, P2)

Description

[ekrock's old account (dead)]

This is a new bug report to track an issue that the fix for bug 55244 apparently 
didn't fully address. It is reported that if you reload a page with 
a named-anchor URL, page displays at top, not at anchor point, even after bug 
55244 has been checked in:

-----------------------------------------------------------------------------
------- Additional Comments From Boris Zbarsky 2000-10-12 10:28 -------

Hmm.  I'm still seeing a problem related to this (using the 2000101208 build).
Go to:

http://www.w3.org/TR/html4/

scroll down to the "Full Table of Contents" and click on one of the links that
are not top-level (eg.  "Copyright Notice" under "About the HTML 4
Specification" heading).

Mozilla will go to the right page, but not scroll to the anchor.  If I just type
the URL in the url bar or into the open location window, it works fine.

Also, if I go to a named anchor and then reload the page, I get scrolled back to
the top.  This is patently wrong.

Should I file a separate bug, or should this one be reopened?

------- Additional Comments From Jeffrey Baker 2000-10-12 10:33 -------

bzbarsky is right.  Named anchors work within a single page, but not
page-to-page.  His w3c testcase is a good one.

-----------------------------------------------------------------------------

Already opened bug 55244 to track the "surfing to URL with named anchor on other 
page doesn't work" problem.

Comment 1

[ekrock's old account (dead)]

Marking P2. High-profile backward compatibility with expected behavior for all 
browsers (reload should take you right to where you are already, including any 
named anchor, not drop you back at the top of the page by ignoring the anchor). 
Marking 4xp, html4, rtm, regression.

Comment 2

[buster]

WMF WinNT debug build from today's bits (10/12/00 around 10:00am)

Comment 3

[Boris Zbarsky [:bzbarsky]]

Broken on Linux 2000101208 and 2000101212 builds.

Comment 4

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Broken on NT debug trunk mozilla build around 12:00.

Comment 5

[Samir Gehani]

Reassigning to component owner may not get us far since it will add to Clayton's
list.  Eric, I'm reassginging to you to find the appropriate owner.  (See
comments by dveditz in cousin bug 56285 2000-10-12 12:17.)

Comment 6

[ekrock's old account (dead)]

karnaze agreed to find an owner for this. --> karnaze

Comment 7

[buster]

this is probably adam as well as 56287, though session history might be
involved.  What happens if you hit "back" or "forward" to get to a URL with an
anchor, instead of reload?

Comment 8

[Boris Zbarsky [:bzbarsky]]

Hitting back or forward seems to sometimes work.  That is, if I click on a URL
with an anchor and end up at the top of the page then hit back then hit forward,
I am still at the top of the page.

If, on the other hand I end up at the top of the page, then go to a different
anchor on the same page, then hit back, I get scrolled to the proper place on
the page and after that going back or forward always puts me at the right spot
with that URL.  So the scroll position is being remembered properly in the
history.....

Comment 9

[Adam Lock]

This bug is another facet of 56285. Marking it as a DUPLICATE.

*** This bug has been marked as a duplicate of 56285 ***

Comment 10

[Loco]

Yup.  VERIFIED.

Comment 11

[Heikki Toivonen (remove -bugzilla when emailing directly)]

SPAM. HTML Element component deprecated, changing component to Layout. See bug
88132 for details.