1.39 KB, application/gzip
Overview: DOM2 specifies that event.relatedNode should be present in mouseover and mouseout events. This is not the case. Steps to Reproduce: View the webpage. Move the mouse and watch the statusbar text. Actual Results: event.relatedNode is undefined in mouseover events. Expected Results: event.relatedNode should contain the node which is about to be entered. Build Date & Platform: M16, WinNT 4
*** Bug 42828 has been marked as a duplicate of this bug. ***
Joki, I belive this belongs to you. Reassgning
Assignee: jst → joki
this doesn't appear to be reported elsewhere. confirmed with 062808 build on NT
Status: UNCONFIRMED → NEW
Ever confirmed: true
Temporarily handling joki's bugs...
Status: NEW → ASSIGNED
I think this bug is invalid (maybe it became invalid because of changes in the DOM spec?). relatedNode property should appear only with mutation events, but mouse movement is not a mutation event. However, mouse events have a property relatedTarget, which is set correctly (you can test by changing relatedNode to relatedTarget in the URL). Marking INVALID. If you think I am in error, please reopen the bug and state why you think this is a valid bug. Thank you.
Assignee: joki → heikki
Status: ASSIGNED → NEW
I do this all the time, NOW marking INVALID...
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
Correct. At the time, I reported the bug, I had only the candidate recommendation of DOM2. Between these versions relatedNode "mutated" into relatedTarget. Thanks.
Source code problem not ours. Marking as Verified.
Status: RESOLVED → VERIFIED
ksosez: If it is a source level problem it still must be verified. If you are not qualified, someone who can code must look at the fix and say it is verified.
QA Contact Update
QA Contact: vidur → vladimire
You need to log in before you can comment on or make changes to this bug.