298477 - relatedTarget is never set for mouseover event

Status: RESOLVED FIXED

(Core :: DOM: Events, defect)

Description

[Dave Townsend [:mossop]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050622 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050622 Firefox/1.0+

mouseover events never have the relatedTarget set making it impossible to
determine where the mouse came from

Reproducible: Always

Steps to Reproduce:
1. Open the upcoming testcase.
2. Move mouse around document.
Actual Results:  
The input box showing the relatedTarget for mouseout events updates fine while
the one for mouseover events always show [null].


Expected Results:  
The relatedTarget for mouseover events should be the DOM node that the mouse
came from.

This is a regression, the test case appears to work, in firefox 1.0.4, though it
has some problems there for some reason.

Comment 1

[Dave Townsend [:mossop]]

Attachment: testcase

Comment 2

[Dave Townsend [:mossop]]

Note that I do not believe this is a duplicate of bug 112553. There the
relatedTarget is set in all but a few cases, here its all the time, also there
the mouseout event is similarly affected while here it isnt.

Comment 3

[Dave Townsend [:mossop]]

Fixing accidentally changed flag, apologies for the spam

Comment 4

[Dave Townsend [:mossop]]

Tracked regression point to between the builds from 28th March and 29th March.
This points to the fix for bug 284664.

Comment 5

[Dave Townsend [:mossop]]

Attachment: testcase 2

This is an alternate testcase that logs what the mouseover and mouseevents
think is happening to the mouse pointer. Move the mouse over the table below
the text boxes to see logs of the events.

Comment 6

[Mats Palmgren (inactive)]

Attachment: Patch rev. 1

I have tested all URLs/testcases linked to via bug 284664 too and I didn't see
any regressions by this patch.

Comment 7

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Comment on attachment 187080 [details] [diff] [review]
Patch rev. 1

major DHTML regression

Comment 8

[Dave Townsend [:mossop]]

This patch fixes the bug for me

Comment 9

[Mats Palmgren (inactive)]

Dave, thanks for the excellent bug report!

Checked in on trunk at 2005-06-24 18:32 PDT

-> FIXED