66208 - Rollover images preloaded via JS aren't cached.

Status: RESOLVED DUPLICATE of bug 20110

(Core :: Networking: Cache, defect)

Description

[Brice Ruth]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; N; PPC; en-US; m18) Gecko/20010119
BuildID:    2001011912

Can't seem to nail down what's going on, but it appears that even though the
preload script appears to cause Mozilla to grab the images (after doc loads,
progress bar shows activity), rolling over images causes Mozilla to contact the
server again. Rollover JS code is unmodified Dreamweaver 4.  about:cache shows
images cached, but after rolling over images & checking about:cache again, no
images show any usage.

Reproducible: Always
Steps to Reproduce:
View pages with preloaded rollovers ...

Comment 1

[Brice Ruth]

All right - I have some more info & a URL where this behaviour can be observed.

Info: When first accessing the URL (or opening the file locally from the HD)
everything works fine, apparently ... however, simply hitting 'reload' and
observing the rollover behaviour makes the problem apparent (again, over the
network or locally).  The very first time a browser window encounters the URL,
after preloading of images is completed 'Document: Done' appears in the status
window.  After reload, this isn't the case and observing the progress bar shows
that every rolled over image causes Mozilla to contact the server (or load fresh
from HD).

URLs:
http://www.projkts.net/mozilla_bugs/keys_top/imageready.html
http://www.projkts.net/mozilla_bugs/keys_top/dreamweaver.html

The first URL is the original Photoshop file exported from Imageready with
rollovers and JavaScript coding ala Adobe.  The second is courtesy of a
Dreamweaver plugin designed for Lynda.com that takes Imageready JavaScript and
converts it to standard Dreamweaver JavaScript.  I've included both since the
behaviour is observable on both and both use slightly different methods to
complete the same task.

Comment 2

[Jure Repinc (JLP)]

Marking as duplicate of bug 65921 (Javascript rollovers make images dissappear.)

*** This bug has been marked as a duplicate of 65921 ***

Comment 3

[Brice Ruth]

I disagree.  Reading bug 65921 and the other bugs referenced within, this
doesn't seem to be covered.  I don't see any images disappearing nor being
replaced by alt text ... also, the first time the page is loaded in a particular
instance of a browser window, the rollovers work just fine - no matter the speed
of onMouseOver events firing (its actually pretty darn quick).  On reload (or
after following a link and the same template being loaded with different
content) the bug is made apparent.

Note: I've reported a couple bugs now and each time I have, the powers that be
seem to be over-eager to mark dups ... let's be a tad more careful and analyze
the problems more carefully.

Comment 4

[Bradley Hart]

I see this also, Mac OS 8.6, build 2001012204. Dupe was incorrect, confirming.

Comment 5

[janne hayrynen]

read bug 20110 (very slow, cpu-hogging mouseover of javascript buttons).
the summary might be a bit misleading, but i think it addresses this problem and
this should be marked as duplicate of it.

Comment 6

[janne hayrynen]

from bug 20110:

------- Additional Comments From Jeffrey Baker 2000-11-09 17:29 -------

This is re-fux0red on Linux 2000-11-09-08 Trunk and 2000-11-09-09 MN6.  To
reproduce:

1) load http://xml.apache.org/
2) Hit the reload button
3) Move the mouse around on the left-hand navigation bar.

Result: an If-Modified-Since request is generated for each event handler, and
some images change from being present, to being not found and represented by
their ALT text.

Expected result: images loaded from image cache.

This is a serious regression.  Can't ship with a browser that hammers innocent
sites.

Comment 7

[Brice Ruth]

Seems like we found a winner.

*** This bug has been marked as a duplicate of 20110 ***