Open
Bug 185919
Opened 23 years ago
Updated 3 years ago
Mousemove event doesn not bubble up from an IFRAME
Categories
(Core :: DOM: Events, defect, P5)
Tracking
()
NEW
People
(Reporter: vladimire, Unassigned)
References
(Blocks 1 open bug, )
Details
There is no mouse move event fired on the IFRAME element when the mouse is
moving inside of it.
Testcase:
http://bugzilla.mozilla.org/attachment.cgi?id=33247&action=view
Also check out the sample URL
| Reporter | ||
Updated•23 years ago
|
Priority: -- → P3
Comment 1•23 years ago
|
||
I am not sure who is in the DIG group at this time; CC'ing Kevin, who might
know. Bug 78976 is marked DIGBug+, but not sure for what reason exactly, so
clarification is needed.
Assignee: jkeiser → saari
You need to implicilty add the mousemove events into the document body of the
iframe. Iframes are not Divs. They have their own JS context.
| Reporter | ||
Comment 3•22 years ago
|
||
Even though they have their own JS context, iframe is displayed as part of the
document, and if you want to know if the mouse is moving over it, you should be
able to know (for example in case you want to drag something across the iframe).
I cant find any specifications saying anything for or against this, but if you
know why it is bad, please let me know. Perhaps iframe.onmousemove is invalid,
even though it does make sence to me, but document.onmousemove should still be
firing even though the mouse is over the iframe. I think that in the case where
mouse is over the iframe mousemove should fire at both the top.document and at
iframe.document.
Comment 4•20 years ago
|
||
This also appears to be broken for event capture, as well as event bubbling. I
think some special code to allow for cross-context event bubbling is required
here, but missing.
Updated•16 years ago
|
Assignee: saari → nobody
QA Contact: vladimire → events
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•