Closed Bug 19550 Opened 25 years ago Closed 25 years ago

Cached images

Categories

(Core :: DOM: Core & HTML, defect, P3)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Windows 98
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 13325

People

(Reporter: mattsch, Assigned: pnunn)

References

(
URL
)

Details

Javascript isn't caching images for mouseovers and picture changes.
Assignee: gagan → vidur
Component: Cache → DOM Level 0
Sounds DOM related. => Vidur.
This could also be simply the lack of any caching at all, for any files -
which still seems to be the case.

That is bug 8305 - "[Arch] Cache needs to be implemented." - P2, M12, ASSIGNED.
Caching of images called by javascript may have additional wrinkles, but
testing for that will have to wait.

The conservative move here would be to make this bug depend on bug 8305,
so that this will get an independant check once 8305 is fixed.
Summary: Cached images → [wip+rods]Cached images
Assignee: vidur → fur
It is not that JS needs to cache images, it's that we need an image cache. Then
when JS goes to get an image it comes from the cache, but this is transparent to
JS. I am assigning this over to fur as an additional test case for the image
cache or he can mark it as a duplicate.
Summary: [wip+rods]Cached images → Cached images
changed summary
First, it's not clear what the bug is since there's no description of the
problem in the report.

Second, the network memory cache has nothing to do with the image
cache.  Assigning to pnunn...
Assignee: fur → pnunn
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
rods:

There is an image cache. It was never disabled.
Currently the reload policy on all images
(except animated gifs) is set to get the
image from the cache if it exists in the cache.
If not, get it from the server.

Animated gifs get the image from the netlib cache for every
loop. Since this cache doesn't exist yet, the image is
retrieved from the server.

I'm closing this as invalid, unless someone can further
clarify the problem.
-pn
Status: RESOLVED → REOPENED
I'm reopening this one. Just because the analysis of
the problem is incorrect doesn't mean there isn't a problem
with js images.

-pn
Resolution: INVALID → ---
Clearing INVALID resolution due to reopen.
Sounds like a dup of 13325.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
I agree. It does sound like a dupe.
-p

*** This bug has been marked as a duplicate of 13325 ***
Status: RESOLVED → VERIFIED
verified duplicate of 13325
You need to log in before you can comment on or make changes to this bug.