Open Bug 1689777 Opened 4 years ago Updated 4 years ago

overflow:clip causes transformZ to stop applying to UI but not to the rendered result

Categories

(Core :: Layout, defect)

Firefox 84
defect

Tracking

()

Tracking Status
firefox-esr78 --- wontfix
firefox85 --- wontfix
firefox86 --- wontfix
firefox87 --- fix-optional

People

(Reporter: quietpianist-git, Unassigned)

References

Details

(Keywords: regression, regressionwindow-wanted)

Attachments

(2 files)

Attached file index.htm

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

Create a div positioned absolutely and transformed such that it's only translated along the Z axis then scaled back on the X and Y axis so that no size change is perceivable. Add a clickable anchor tag to it. Add a parent to the div that has a fixed height, "transform-style: preserve-3d;", and "overflow:clip;". Add a sibling to this div with a fixed height larger than the page. Add a parent to both of these elements with a perspective rule, "height: 100vh;" and "overflow: auto;".

Actual results:

The content should scroll with parallax as the page is scrolled and appear correct, but clicking on the anchor does nothing because the actual clickable area of the anchor is positioned in the location it would've been before being translated along the Z axis.

Expected results:

The clickable part of the anchor tag should reside over the visible part of the anchor tag.

Status: UNCONFIRMED → NEW
Has Regression Range: --- → yes
Has STR: --- → yes
Component: Untriaged → Layout
Ever confirmed: true
Keywords: regression
Product: Firefox → Core
Regressed by: 1635473

Those patches basically renamed -moz-hidden-unscrollable to clip, but it seems the problem was pre-existing. I can reproduce it in Firefox 78 with this test-case.

No longer regressed by: 1635473
See Also: → 1689805

(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)

Created attachment 9200185 [details]
Testcase with -moz-hidden-unscrollable.

Those patches basically renamed -moz-hidden-unscrollable to clip, but it seems the problem was pre-existing. I can reproduce it in Firefox 78 with this test-case.

Yes, I can also reproduce the issue on Nightly(20171101101044) with force WebRender enabled.

QA Whiteboard: [qa-regression-triage]

I can confirm that I could reproduce this issue on Firefox 78.7 esr, Firefox 85, Firefox 86 beta 4, and Nightly 87.0a1 (when using the test case from Comment 2). I could also reproduce it on older versions like Firefox 60.0.1.

Emilio, considering this is not a recent regression, is it still a candidate for regressionwindow-wanted? If yes, could you please advise on how far should I go with the regression?

Thanks!

Yeah, having a regression range would be amazing... As for how far to go I don't know, I'd probably try firefox 40-ish... If it still repros there it's probably not worth finding the precise range (or it might not be a regression at all)

Flags: needinfo?(emilio)

(In reply to Emilio Cobos Álvarez (:emilio) from comment #5)

Yeah, having a regression range would be amazing... As for how far to go I don't know, I'd probably try firefox 40-ish... If it still repros there it's probably not worth finding the precise range (or it might not be a regression at all)

Using the test case from Comment 2, I was able to reproduce the issue all the way to Firefox 35.

(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)

Created attachment 9200185 [details]
Testcase with -moz-hidden-unscrollable.

Those patches basically renamed -moz-hidden-unscrollable to clip, but it seems the problem was pre-existing. I can reproduce it in Firefox 78 with this test-case.

Just to note, I thought I had tested with overflow:hidden before and got different results which is why I was using clip, but after testing again the issue apparently also manifests when using hidden with no apparent difference from clip, so the issue does not appear to be specific to clip.

FWIW, the testcase here also has somewhat different behavior in Safari vs Chrome. I haven't studied it further to figure out which (if either) is more correct.

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: