Closed
Bug 268539
Opened 20 years ago
Closed 19 years ago
[EVENTTARG]-moz-opacity breaks mouse input for floated elements on the same line
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Core
DOM: UI Events & Focus Handling
Tracking
()
RESOLVED
INVALID
People
(Reporter: moz-bugs, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(1 file)
|
518 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040926 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040926 Firefox/0.10.1 An element floated on to the same line as a transparent element loses mouse events as far as I can tell. I will attach a testcase. (I haven't tried it using absolute positioning instead of floating, but assume the same thing occurs.) Reproducible: Always Steps to Reproduce: 1. Open the testcase I am about to attach 2. Attempt to click on the floated link Actual Results: Nothing (if you double click, the last word in the transparent text is selected). Expected Results: Followed the link. Possibly related to bug 234399?
| Reporter | ||
Comment 1•20 years ago
|
||
Summary: -moz-opacity breaks mouse input for floated elements on the same line → [EVENTTARG]-moz-opacity breaks mouse input for floated elements on the same line
Comment 2•20 years ago
|
||
Confirming, but this is basically the same issue as bug 191830, in a slightly different context. The proposed solution for that bug doesn't really address this one (since it would paint correctly, but the z-ordering calculation used for events would still put the float below the div with a view).
Comment 4•19 years ago
|
||
In fact, this is the same story as bug 275251, when removing the opacity, the link can be clicked upon. See bug 191830, comment 34 and bug 191830, comment 35. Resolving to INVALID.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•