Closed
Bug 75036
Opened 23 years ago
Closed 23 years ago
need to flush chrome images after theme switch
Categories
(Core Graveyard :: Skinability, defect)
Core Graveyard
Skinability
Tracking
(Not tracked)
People
(Reporter: hewitt, Assigned: pavlov)
References
Details
(Whiteboard: [cache])
To quote Hyatt from an e-mail that just went around: There does need to be a way to flush all chrome images (or failing that, all images) from the memory cache when you switch skins. This was dropped on the floor when libpron landed, and now skin switching has regressed.
Adding nsbeta1 keyword since this is important for skin switching.
Keywords: nsbeta1
nsCacheService has methods for evicting all entries for a given device, and nsCacheSession has methods for evicting all entries for a given clientID (say, ImgLib). If ImgLib gets notified that chrome images need to be flushed, it can call EvictEntries() on it's cache session. Oops. I just checked nsCacheSession.cpp, and EvictEntries() is not implemented. That will be easy to fix, because the underlying mechanism in nsCacheService and nsMemoryCacheDevice is already in place. I might be able to get this in this weekend.
Whiteboard: [cache]
Comment 3•23 years ago
|
||
This was broken by the libpr0n landing. libpr0n needs to fix it by giving me an API to call. Over to pav.
Assignee: hyatt → pavlov
I marked this bug as depending on bug 75171 "implement nsCacheSession::EvictEntries()". I have a proposed patch in that bug, and I'm just waiting for review and superreview.
Assignee | ||
Comment 5•23 years ago
|
||
fixed. dup of 75181 *** This bug has been marked as a duplicate of 75181 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified dup.
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•