W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2019

Re: [csswg-drafts] [css-transforms-2] Is it necessary to serialize all 3 components of translate given the 3rd component is 0px (#3305)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 09 Oct 2019 22:07:06 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-540223791-1570658825-sysbot+gh@w3.org>
> This issue is about the translate, rotate, scale properties, not the transform property's functions. The suggestion is not that Blink change the transform property "non-binding hint" behavior; simply that translate etc. need not carry that behavior forwards as there is no web-compat need; authors can use will-change (or a paused animation) as a standards-based approach.

Right, I understand. But I don't like behavior being inconsistent when consistency isn't too bad, even if it's with a legacy bug.

That said...

> I would like to make this change. The only reason we didn't already do it is out of concern for performance compatibility, and we already shipped the change for some low-memory devices.


> All 4 browser engines serialize the gCS result for transform: scale3d(3, 2, 1) as matrix(3, 0, 0, 2, 0, 0), i.e. they don't report a matrix3d result.

both argue that the quirk should be removeable, which is great! If that's the case, happy to change all the supporting specs to match, and only consider something 3d if it's actually outside the screen's plane.

GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3305#issuecomment-540223791 using your GitHub account
Received on Wednesday, 9 October 2019 22:07:08 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:54 UTC