533293 - javascript onmouseover object is persistent

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Amod Mulay]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5

onmouseover object is persistent even when we are not hovering over a particular text(that genrated the onMouseOver)

This is happening even when the particular tab is closed and we are browsing a new tab

Subsequent onMouseOver events are suppressed

Reproducible: Always

Steps to Reproduce:
1.Start firefox
2.mouse over any section of screen (we initially get empty mouseover text box)
3.mouse over on any link with an active onMouseOver event.
4.mouse over elsewhere on the screen and the same text as the previous mouse over appears
Actual Results:  
same text as the previous mouse over appears

Expected Results:  
mouse over on arbitrary parts of screen should not genrate onMouseOver events

nothing
no onMouseOver text/event should occur

Comment 1

[Amod Mulay]

Attachment: shows persistence on mouseover text

Comment 2

[Amod Mulay]

Attachment: another example of text persistence

Comment 3

[Amod Mulay]

text not shown in another window

Comment 4

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html

Comment 5

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 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.

Comment 6

[Amod Mulay]

This bug seems to be fixed from FF version 3.6 onwards.
Have not tested with FF4 beta.