Open Bug 1738017 Opened 3 years ago Updated 1 year ago

Incorrect mouse event with elements stacked and preserve-3d

Categories

(Core :: Web Painting, defect, P3)

Firefox 93
Desktop
Windows 11
defect

Tracking

()

Tracking Status
firefox-esr91 --- wontfix
firefox-esr102 --- affected
firefox104 --- wontfix
firefox105 --- wontfix
firefox106 --- wontfix
firefox107 --- wontfix
firefox108 --- wontfix

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

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.

Component: Untriaged → Web Painting
Product: Firefox → Core
Component: Web Painting → DOM: Events
OS: Unspecified → Windows 11
Hardware: Unspecified → Desktop
Component: DOM: Events → Layout
Severity: -- → S2
Assignee: nobody → mikokm
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

Possibly same issue as bug 1715796.

Priority: -- → P2

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/

See Also: → 1715796
Status: ASSIGNED → NEW
Assignee: mikokm → nobody
Component: Layout → Web Painting

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.

Regressed by: 1208673
See Also: → 1226904

Set release status flags based on info from the regressing bug 1208673

Set release status flags based on info from the regressing bug 1208673

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

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.

Severity: S2 → S3
Flags: needinfo?(tnikkel)
Priority: P2 → P3
Keywords: regression
See Also: → 1843728
You need to log in before you can comment on or make changes to this bug.