Incorrect mouse event with elements stacked and preserve-3d
Categories
(Core :: Web Painting, defect, P3)
Tracking
()
People
(Reporter: demanghonj, Unassigned)
References
(Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
I stacked element with position absolute, I set the css property transform-style: preserve-3d and I add click event listener on each element stacked.
Example: https://jsfiddle.net/v6qcemdh/
Actual results:
The click event is executed on hidden element
Expected results:
The click event should be executed on the visible element
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Web Painting' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Possibly same issue as bug 1715796.
Updated•3 years ago
|
Reporter | ||
Comment 3•3 years ago
|
||
I confirme that is the same issue as bug 1715796.
I implemented the workaround with display:none or mouse-pointer: none to jsfiddle: https://jsfiddle.net/aw0th7cx/1/
Updated•3 years ago
|
Updated•3 years ago
|
Comment 4•2 years ago
|
||
Based on regression testing it looks like bug 1208673 made us go from hitting the div 9 to hitting none of the divs. And then bug 1226904 made us go to hitting div 5.
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Set release status flags based on info from the regressing bug 1208673
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Set release status flags based on info from the regressing bug 1208673
Comment 7•2 years ago
|
||
Timithy, we have two bugs for the same issue and both of them have a testcase (but bug 1715796 is still marked as UNCONFIRMED). Can we have only one duped over the other? Is that really a P2/S2? Thanks
Comment 8•2 years ago
|
||
This is probably S3. Regressed 7 years ago and we haven't got many reports. Bug 1715796 could be a different issue I'd have to look in more detail. To mark that bug confirmed I'd want to dissect the testcase and confirm that our behaviour is incorrect.
Updated•2 years ago
|
Updated•1 year ago
|
Description
•