Closed Bug 25395 Opened 25 years ago Closed 24 years ago

Clicking links after back during reflow reload page

Categories

(SeaMonkey :: General, defect, P2)

x86
Windows 95
defect

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: stephena, Assigned: jud)

References

()

Details

Let me see if I can get this across clearly.

1) Start mozilla and bring up a lengthy page with links near the top.  CNN's 
website on a 56K modem does the trick for me.
2) After it has finished loading, click on one of the stories links.
3) After the story is finished loading, click the back arrow.
TIMING IMPORTANT
4) While the page is loading again and reflowing, as soon as the links at the 
top show up (like myCNN, Video, Audio, etc.) click on one of them.

What should happen is mozilla should stop loading CNN's front page and start 
taking steps to load the link you just clicked.  What happens is that it stops 
loading the page, but instead of starting to load the link, it starts to load 
the CNN front page all over again.

I can reproduce this pretty religously in M13 on Win95.  This bug report may be 
a dup, but the bugzilla query system is down (bug 25393) so I dunno.  It may 
seem like a trivial bug, but it's fairly annoying, and it may be hiding a 
mozilla crash (bug 22092)
Sounds like a Web shell issue
Assignee: troy → travis
Let's deal with this post beta 1 ...
Component: Layout → Browser-General
Priority: P3 → P2
Target Milestone: M15
I guess you guys know better than I, but this particular problem is a real PITA 
for me.  Those of use without 56K modems can wait a good long while while some 
pages load from a back operation.  This bug means we cannot click on successive 
links until the page is done laying out.  This makes sites like CNN where I 
regularly peruse all the major headlines a serious headache.  For me, this is a 
dogfood issue, but as I say, I defer to those who know better.
Move to M16 for now ...
Target Milestone: M15 → M16
M16 has been out for a while now, these bugs target milestones need to be 
updated.
I can't reproduce this. 

Stephan, can you try with a newer build and mark RESOLVED if the bug is gone?
Target Milestone: M16 → ---
Target Milestone: --- → Future
The back behavior is still flaky, but it is no longer well described by this 
bug.  Marking as resolved.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Marking verified in the Aug 24th build.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.