Closed
Bug 271443
Opened 20 years ago
Closed 19 years ago
Throbber never stops on pages with missing images
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mpaugh, Assigned: bugs)
Details
Attachments
(1 file)
55 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 (Only tested on local pages (with local image links) since that way I know that it's not a server issue.) When I load a local page containing a missing image (that is, I specify a SRC that doesn't exist), sometimes the page never finishes loading (throbber never stops; progress bar at the bottom never goes away; stop button is still enabled) as if it is busy waiting around for my hard drive to find the missing image. :) This only happens sometimes; I'd estimate about 50% of the time. Reproducible: Sometimes Steps to Reproduce: 1. Create a local HTML page with an <img src="dummy.jpg"> type link. 2. Load in Firefox. 3. If that doesn't do the trick, reload a few times until the problem occurs. For me it seems to happen about every other time that I reload. So: Reload, it works; reload, throbs forever; reload, works... etc. Actual Results: Page loads essentially forever (I haven't tried leaving it for a couple of hours to see if it will really go "forever"). Stop button works. Expected Results: Page should finish loading and stop. =)
confirming on Mac trunk - I need to reload to see the behavior. Hardware->All, OS->All, Version->Trunk
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
Comment 3•19 years ago
|
||
WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050504 Firefox/1.0+
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Updated•18 years ago
|
QA Contact: bugzilla → toolbars
You need to log in
before you can comment on or make changes to this bug.
Description
•