Closed
Bug 179981
Opened 22 years ago
Closed 22 years ago
Page never finishes loading
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tracking
(Not tracked)
People
(Reporter: nateops, Assigned: susiew)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:0.9.4.2) Gecko/20020220 CS 2000 7.0/7.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:0.9.4.2) Gecko/20020220 CS 2000 7.0/7.0
When I bring up http://cbs.sportsline.com/ in any Gecko browser under Windows
XP, the entire page is displayed in a reasonable amount of time, but the browser
seems to still be waiting for further data. In Compuserve 7, the compuserve
logo in the top right continues to display the particle of light anaimation that
indicates it is working. In Phoenix 0.3, the red "Stop" button never greys out
and the progress bar in the lower right never goes away. In Mozilla 1.1b, the
red-dinosaur animation in the upper right never goes away, the status bar
continues to display "Transferring data from cbs.sportsline.com..."
indefinitely, and in tabbed browsing the arrow-circle animation on the tab
continues indefinitely. There don't appear to be any looping gif-animations on
the page.
This effect does not occur in IE. I kept each of these browsers open for 10+
minutes, and the session did not time out.
Reproducible: Always
Steps to Reproduce:
1. Go to http://cbs.sportsline.com/ in CS 7, Phoenix, or Mozilla on Windows XP
Actual Results:
The page loaded and displayed the expected data but never indicated completion.
Expected Results:
After the page and it's elements were downnloaded, the "data transfer in
progress" sigils should have reverted into their quiescent state.
Phoenix - default theme
Mozilla - theme "Negative Modern"
CS build 4114.123 (32-bit)
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 81980 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•