Closed
Bug 103902
Opened 23 years ago
Closed 23 years ago
cache setting "every time I view the page" causes chrome mousoever flickering
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: MozillaUser, Assigned: pavlov)
References
Details
on Windows 95 in build 2001100903 (and all builds for many moons) Go into Preferences -> Advanced -> Cache and choose "Every time I view the page" Exit mozilla completely, then start mozilla again (that cache pref is not activated unless you do so) Move the mouse over the navigation buttons to get he mouseover effect. The buttons will flicker. The effect is greatly exagerated if you mouseover the navigation buttons while loading a new page. The buttons can remain invisible for several seconds
That's very odd. The HTTP cache validation preference should have nothing to do with how ImgLib loads the chrome images. Pav, any ideas?
Assignee: gordon → pavlov
Component: Networking: Cache → ImageLib
QA Contact: tever → tpreston
Comment 2•23 years ago
|
||
How odd. I can confirm seeing this effect, build 2001100903, Win98.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•23 years ago
|
||
I see this behavior on Mac OS X build 2001-10-09-04-0.9.4, Linux build 2001-10-09-04-0.9.4 and w2k build 2001-10-08-05-0.9.4, changing OS to all
OS: Windows 95 → All
Comment 4•23 years ago
|
||
I get the "flickering" behavior on other chrome elements too such as sidebar tabs, it's rather nasty. I've created an AVI that shows this if anyone needs (800K, maybe too big to add as attachment here).
Comment 5•23 years ago
|
||
Confirming Windows 2000 16,24,32 bit video settings. Using mozilla win32 nightly build 2001102708. Is everything including chrome going through the cache manager?
Comment 6•23 years ago
|
||
This WFM win XP build 2001111303, reporter are you still seeing this?
Reporter | ||
Comment 7•23 years ago
|
||
Yes, I still see this on Windows 95 using build 2001111303 I strongly suspect that this happens for the same reason that bug 108161 happens. After all, the images are being changed with javascript in exactly the same way, its just that that bug deals with the symptoms of a webpage doing it, and this deals with the symptoms of chrome doing it.
James: err no, images are not being changed via javascript the same way as with webpages. It is being changed via css :hover rule though I think it is still related to bug 108161.
Assignee | ||
Comment 9•23 years ago
|
||
this should have been fixed as a result of the checkin for bug 108161 since local images won't get reloaded as a result of validate_always, etc being set.
You need to log in
before you can comment on or make changes to this bug.
Description
•