Closed
Bug 155239
Opened 23 years ago
Closed 22 years ago
JavaScript Rollover Preloading Hangs Status Bar
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
RESOLVED
DUPLICATE
of bug 166428
mozilla1.4beta
People
(Reporter: joseph, Assigned: jdunn)
References
()
Details
Attachments
(1 file)
740 bytes,
text/html
|
Details |
When Mozilla 1.0 (and other versions, including past & current trunk builds)
uses BODY ONLOAD to preload a series of images for use in a "rollover"
situation, the blue bar that indicates page loading progress (in the lower-right
corner of the screen) hangs at 100%. The "Transferring data from X..." message
in the lower-left also stays on screen.
This error does not appear for me when only ONE image is preloaded. When 2-3
images are preloaded, the error happens sporadically, and when 4+ images are
loaded (for example, a large toolbar), the error is consistent. However, the
entire rollover procedure does work as intended -- it's just a status bar issue.
This error appears on my own site <http://www.joseph.ca> as well as rollover
demo sites like <http://www.uwplatt.edu/~web/wtc/rollover-final.html>, and
presumably any site that preloads images for rollovers. I've tried different
variants of preloading code on my site, from hand-crafted to
Dreamweaver-generated. It can't be a network error because I can get the same
problem from local browsing via my hard drive.
So my questions are:
a) Is this a universal error in Mozilla?
b) Is there "better" preloading code that I should be using instead?
-Joseph
P.S. My site has several JavaScript functions -- the one that's causing this
error is welcomeMe(), called by BODY ONLOAD.
Comment 1•23 years ago
|
||
Confirmed.
Mozilla 1.0
Windows 98
Markign new.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac System 9.x → All
Hardware: Macintosh → All
"mass" re-assigning of bugs from pav to myself
Assignee: pavlov → jdunn
I created a very simple testcase (single onload image) that
shows the problem. This is essentially the same as one of the
originally submitted tests, just paired down for debugging purposes.
This was fixed by jag's checkin for 166428.
Any trunk build after 5/13 should now work.
THANKS JAG!
*** This bug has been marked as a duplicate of 166428 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Core → Core Graveyard
Updated•7 years ago
|
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•