W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2017

Re: [csswg-drafts] [css-transforms] Spec and blink implementation of transform-box for SVG elements differ

From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Mon, 27 Mar 2017 20:27:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-289575556-1490646456-sysbot+gh@w3.org>
Thanks for those numbers Frederick.

I assume the jump in the stats from the middle last week is related to the usage counter expanding from Chrome Canary users to Chrome Beta users?  (And so the later numbers are *probably* more representative of the wider web...)

Do you have a separate tracker for `transform-box` itself?  With Firefox's `transform-box` support ready to roll out in v55, I suspect we'll see an increase in usage of `transform-box: fill-box` over the coming months, as devs fix transforms that were designed for Chrome but look broken in Firefox.

Given approximately 0.01% usage, would it be worth having some sort of organized education & transition plan, such as console warnings on sites that trigger that measurement?  In addition to warning that the transformation of some elements might change in a future version, it could provide a link to information about the `transform-box` property  (to [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/transform-box) or the spec).

Of course, once we get a clear commitment that Blink is going to implement `transform-box`, I know many "thought leaders" in the SVG web animation community who would happily help get the word out.  But they need a clear, consistent implementation plan from browsers so that they can provide useful advice.

GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/857#issuecomment-289575556 using your GitHub account
Received on Monday, 27 March 2017 20:27:44 UTC

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