Let's say you're on a page, such as:
And you click on the "What's New" link, whose URL is:
It should just scroll you down to the location of that anchor (#new), but
instead, it reloads the page before scrolling down to the named anchor.
Troy, who gets this?
Rick, I don't have much to do with link processing so I'm giving it to you
*** Bug 1560 has been marked as a duplicate of this bug. ***
In addition to forcing a reload, anchor links now don't move to the anchor
after the reload either. See, for example,
This should work for both A NAME="..." and ID="..." anchors.
Re-assigned to email@example.com.
Gagan, is this a netlib bug? Who should get this?
Not netlib for sure. Layout...?
Adding Rick Potts to the cc: list. Maybe the docloader handles this; I dunno.
Here's what happens. The nsHTMLAnchorElement code ends up calling the link
handler and having it handle the link click. The link handler is the Web shell
and it doesn't check for the same URL and a fragment identifier, it just loads
the same document. We don't even seem to respect the fragment identifier so we
just go to the top of the document
I don't know how this used to work. Kipp probably knows. I don't know why things
have changed, but since the Web shell is the link handler I'm assigning it to
Let's try and be adults about this and stop treating this bug like a hot potato
*** Bug 2579 has been marked as a duplicate of this bug. ***
Guys, any chance this could be fixed soon? It's making QA a right pain
in the neck.
Pumping up the priority.
Extra test pages for whoever is implementing this:
Setting all current Open Critical and Major to M3
Fixed so we don't reload the document
Whoops... I take that back. The document still reloads when you hit the back
button after going to a named anchor, when it is moving back to the original
(non-anchor) position. Also, the URL doesn't change when I go to a named
The problems you mention when you reopened the bug are different than the
originally described problem, so I think the right thing to do is to leave this
bug fixed and create additional bugs for the new problems
OK...filed bug 3152 and re-resolved this one.
I can't verify this one, on the 2/10 build the name anchor does not work. More
recent builds don't display the content correctly. Will check in a couple of
name attributes now work on 2/22/99 build, setting bug as verified