Closed Bug 59490 Opened 25 years ago Closed 25 years ago

Navigation is incorrect at the w3 css site.

Categories

(Core :: DOM: Navigation, defect, P3)

x86
All
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: augustmiles, Assigned: radha)

References

()

Details

First I go to http://www.w3.org/ I click on "CSS" in the left column. This takes me to the CSS site for w3 at http://www.w3.org/Style/CSS/ There are several "banners" at the top of the page. Click on "Learning CSS" Now click once on back. Expected result: I should be at the top of the CSS page. What happens I am back on the w3 home page.
*** Bug 59491 has been marked as a duplicate of this bug. ***
The page in question uses an anchor. Back should return to the top of the page (as it did in 4x and does in IE). Confirmed with 2000110604 on Win2k Over to History... OS to All... adding 4xp keyword.
Assignee: asa → radha
Status: UNCONFIRMED → NEW
Component: Browser-General → History
Ever confirmed: true
Keywords: 4xp
OS: Linux → All
QA Contact: doronr → claudius
Hmm. I can reproduce this, but with one caveat. If I wait for the CSS page to load completely and then click the "Learning CSS" link and then click back everything works as it should. If I click on the "Learning CSS" link _before_ the page is completely loaded, Mozilla will go to the anchor correctly, but when I click "back" I see this bug. linux trunk 2000110521.
I can not reproduce the problem. The incomplete loading problem is addressed in another bug. marking this worksforme.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Rashe, do you have what bug number is the other bug? (I just tried and could still reproduce the problem as described by Boris...) CVS build from 20001115 on Win2k
mass-verifying WorksForMe bugs which haven't changed since 2001.12.31. set your search string in mail to "EmperorLondoMollari" to filter out these messages.
Status: RESOLVED → VERIFIED
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in before you can comment on or make changes to this bug.