1910607 - Firefox on mac os does not render -moz-transform css property

Status: RESOLVED FIXED

(Core :: CSS Parsing and Computation, defect)

Description

[vldmr.rr+bus]

Steps to reproduce:

Here is simple example (https://jsfiddle.net/fxtg6c2e/)
HTML: <div id="one">ONE</div><div id="two">TWO</div>
CSS: #one { position:absolute; background-color: blue; -moz-transform: translate3d(0,30px,0);}

Actual results:

On mac os text "ONE" is rendered on top of text "TWO".

Expected results:

On windows text "ONE" is rendered under text "TWO". This same behaviour existed in earlier versions of Firefox on mac os

Comment 1

[Francesco Lodolo [:flod] (OOO July 12–20)]

This is broken in release (128.0.3), beta (129 RC), but working on Nightly (20240729204357).

Not sure if it was fixed (likely), or Nightly has some other setting that avoids the issue.

Comment 2

[Mayank Bansal]

"fixed" by :

Bug 1901497 - Enable -moz- transform prefixes on nightly again. r=webcompat-reviewers,twisniewski

This changes the approach of zoom+moz-transform compat on Nightly, on
the basis that its easier to site-patch stuff that uses both
-moz-transform and zoom (to disable either of them via CSS) than working
around bogus UA sniffing or feature detection that is sorta-reasonable
(like assuming that if "MozTransform" is in the CSSStyleDeclaration
object, then -moz-transform works).

If breakage from this is too severe, or the hypothesis above doesn't
hold, then we need to re-evaluate this in some other way.

Differential Revision: https://phabricator.services.mozilla.com/D216840

Comment 3

[vldmr.rr+bus]

This is still broken in vesrion 131 on mac. It does work on windows

Comment 4

[Daniel Holbert [:dholbert]]

So this is just about whether support for the -moz-transform syntax is enabled or not. We tried to remove support for that syntax (which is why this broke, though not in any OS-specific way); and we've since reenabled it.

Comment 2 indicates when it was reenabled on Nightly; and then it was reenabled for release in bug 1886134 which shipped in Firefox 133. I think we can consider this FIXED by the patch that landed there, but please let us know if this is still looking broken in versions after that.

Comment 5

[Daniel Holbert [:dholbert]]

And for what it's worth, I confirmed that I see expected-results ( "ONE" is rendered under text "TWO" [i.e. the text is separated instead of superimposed]), in 136.0.1 (current release) on macOS.