Closed
Bug 503685
Opened 16 years ago
Closed 9 years ago
Mouse events for CSS :before in iframe in designmode broken: mouseover fires on move, mouseout fires never
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cacyclewp, Unassigned)
Details
(Keywords: regression)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)
In an iframe in designmode the mouse events for a span:before element are broken. mouseover fires for every mouse move (it should fire only for the first move into this element) and mouseout does not fire at all. The events work fine one the element itself, in iframes that are not in designmode, and in the main document. It also works fine in Firefox < 3.5 as well as Google Chrome. Please see the attached testcase/testbed.
This might or might not be related to Bug 502527. These two Firefox 3.5 bugs make it completely impossible to realize tab-like effects in rich text editors where the tabs are not part of the editable iframe content.
Reproducible: Always
Comment 2•16 years ago
|
||
Confirmed on Windows Vista.
Status: UNCONFIRMED → NEW
Component: General → DOM: Events
Ever confirmed: true
Keywords: regression
Product: Firefox → Core
QA Contact: general → events
Version: unspecified → Trunk
Another strange thing: When moving into the span:before in the iframe in designmode, event.relatedTarget refers to an element that is not in the page context. Any access to this object triggers a security error ("Error: Permission denied to access property 'id' from a non-chrome context
Source File: file:///D:/wikEd/testcase%20before%20mouseover,%20mouseout%20001.html
Line: 34"). This seems to be related to bug 101197 (which has not been fixed since its first report in 2001!).
Please could somebody look into this bug as it breaks reference hiding for the Wikipedia rich text editor wikEd.
The testcase is still broken in 3.6a1, but works correctly in 3.7a1pre.
(Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1) Gecko/20090806 Namoroka/3.6a1 (.NET CLR 3.5.30729))
(Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20090927 Minefield/3.7a1pre (.NET CLR 3.5.30729))
Comment 6•9 years ago
|
||
Firefox: 47.0, Build ID 20160604131506
User Agent Mozilla/5.0 (Windows NT 5.1; rv:47.0) Gecko/20100101 Firefox/47.0
I have tested this issue on the latest Firefox (47.0) release and the latest Nightly (50.0a1 - Build ID: 20160627030215) build, but I could not reproduce it. For testing this I have used the provided test cases from comment 1 and comment 4. Mouseover fires only for the first move into the element and mouseout behaves the same.
Cacycle, is this still reproducible on your end ? If yes, can you please retest this using latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).
Flags: needinfo?(cacyclewp)
Comment 8•9 years ago
|
||
Considering this I will mark this issue as Resolved - WFM.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(cacyclewp)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•