Closed Bug 153165 Opened 23 years ago Closed 23 years ago

Session history funky.

Categories

(Core :: DOM: Navigation, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 138491

People

(Reporter: erin, Assigned: radha)

References

()

Details

From Bug 103978: (WinXP, build: 2002053012) http://f1.racing-live.com/en/ CONFIRMED, the back button is greyed out if I visit a link. BUT this is only reproducable if you start with a clean tab or a clean window (i.e. no previous history), if you visit some other site first, and then go to http://f1.racing-live.com/en/ (in the same window/tab) and then click on a link - then the history works as it should. ------- Additional Comment #100 From Frederic Nilsson 2002-06-20 10:37 ------- I'm really sorry for spamming, but the history does not work alright. :) Case A: 1) Go to http://f1.racing-live.com/en/ 2) Click on a news link Case A behaviour: History back is greyed out and empty. Case B: 1) Go to any site, like mozilla.org 2) Paste in http://f1.racing-live.com/en/ in the address field and go there 3) Click on a news link 3) Go back one step - you will be at mozilla.org 4) Go back one step more - you will be on one of the subframes of http://f1.racing-live.com/en/ (looks really weird)
I can confirm the wonky behaviour. I am on the 1.1Alpha W2K build.
I see this on Linux trunk build 2002062011 OS -> All Status -> NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
I have seen this before. If you notice, When you visit this site, the throbber never stops and the icon stays at hour-glass. This indicates that the page is not completely loaded. Infact the throbber never stops at this site or in any of its children, nomatter how long you wait. The network module and thereby session history think that more data is coming and is in a state awaiting more data. When you click on one of the links, session history thinks that this subframe is the awaited data and therefore does not add a new entry to it. The page perhaps has a document.writeln() without a corresponding document.close(). But this problem is specific to this site and because of the factor that the page never stops loading. marking Invalid.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
*** Bug 155614 has been marked as a duplicate of this bug. ***
dupe of 138491. Reopening so I can resolve this as a duplicate.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 138491 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
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.