Closed
Bug 428536
Opened 17 years ago
Closed 12 years ago
Previous state incorrectly (?) cached
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: matt, Unassigned)
References
()
Details
(Whiteboard: [closeme 2013-07-25][FF3.x])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Onmouseout doesn't fire on elements when the window.location is changed. This seems logical, but after hitting the back button the page is returned to the state of events left by the previous onmouseover.
Reproducible: Always
Steps to Reproduce:
1. See http://mpcm.com/ff3b5.html
2. See the onmouseover/out css changes
3. Click on one (loads google)
4. Hit the back button
5. css state should be the one that was active when onclick happened, since onmouseout didn't fire.
Actual Results:
It doesn't seem logical for onmouseout to fire, but perhaps it should as otherwise an incorrect state is allowed, or the cached version is inconsistant. (a timing issue, perhaps not a bug?)
Expected Results:
The "back'd" version should appear as the freshly loaded version. IE has this behavior, perhaps the results of the onmouseout should be calculated and the css/dom changes saved, but other effects quashed...
Comment 1•15 years ago
|
||
This is a mass search for bugs that are in the Firefox General component, are
UNCO, and have not been changed for 800 days and have an unspecified version.
Reporter, can you please update to Firefox 3.6.10, create a fresh profile,
http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you
still see the bug, please update this bug. If the issue is gone, please set the
resolution to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Reporter | ||
Comment 2•15 years ago
|
||
This bug still happens in 3.6.10 on ubuntu.
Upon hitting the back button you can move the mouse over the now green box and watch it go a little wacky.
Version: unspecified → 3.6 Branch
Reporter | ||
Updated•15 years ago
|
Severity: trivial → normal
OS: All → Linux
Hardware: All → x86_64
Comment 3•15 years ago
|
||
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Reporter | ||
Comment 4•15 years ago
|
||
Tested with new profile with 3.6.12 and this is still an issue. Not sure what status flags you need to keep this open and get it resolved.
Updated•15 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: INCOMPLETE → ---
Whiteboard: [CLOSEME 2010-11-01]
Comment 5•12 years ago
|
||
Reporter, can you still reproduce using a current version?
If no, please set status to RESOLVED and resolution to WORKSFORME.
If yes, please provide updated information.
Whiteboard: [closeme 2013-07-25][FF3.x]
Reporter | ||
Comment 6•12 years ago
|
||
This is fixed for backwards navigation, as once the mouse moves (or appears) in the vieport, onmouseout triggers. If you navigate backwards from the menu, it does not fire until the mouse enters the viewport, which seems reasonable.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago → 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•