W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2018

Re: [csswg-drafts] [css-transforms-2] Please remove from drafts: scale, translate, rotate CSS style etc.

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 08 Feb 2018 00:41:50 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-363963029-1518050509-sysbot+gh@w3.org>
The Working Group just discussed `[css-transforms-2] Please remove from drafts: scale, translate, rotate CSS style etc.`, and agreed to the following resolutions:

* `RESOLVED: no change with clarification notes from the issue`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-transforms-2] Please remove from drafts: scale, translate, rotate CSS style etc.<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2126<br>
&lt;dael> ericwilligers: They are valuable. They have the full motoin path and can be independantly animated.<br>
&lt;dael> ericwilligers: I think libraries will find it useful.<br>
&lt;Rossen_> tsr ftw<br>
&lt;dael> TabAtkins: They also let us capture the generally most intuitive ordering without making authors remember it. translate then scale then rotate<br>
&lt;dael> AmeliaBR: They's useful for [missed]<br>
&lt;TabAtkins> +1 to all that AmeliaBR is saying too.<br>
&lt;dael> AmeliaBR: They're useful for animations, you can animate one factor. And they're useful for different transformations assigned with different classes or pseudo classes<br>
&lt;dael> ericwilligers: There's an issue about preserve 3d from fremy but I think that's a different issue.<br>
&lt;dael> fremy: Feel free to disregard mine.<br>
&lt;dael> ericwilligers: Can we resolve to keep properties?<br>
&lt;dael> Rossen_: fremy you said you have your point in the issue...disregard it? Is that what you wanted?<br>
&lt;birtles> The very popular GreenSock Animation (GSAP) also takes this approach of a fixed order of transform components and promotes it as one of its key usability benefits over CSS (although it further breaks these components into x/y/z too)<br>
&lt;dael> fremy: I agree it's a different issue and shouldn't be in that topic.<br>
&lt;fantasai> +1 to smfr<br>
&lt;dael> smfr: I don't think anybody on this call agrees with the issue. I think we're all okay with separate properties.<br>
&lt;dael> AmeliaBR: I did have a couple comments in there suggesting clarifications in the spec.<br>
&lt;dael> Rossen_: Does anyone support the issue to remove?<br>
&lt;dael> Rossen_: Obj to resolve no change?<br>
&lt;dael> fantasai: No change add clarifying notes.<br>
&lt;dael> Rossen_: Are the notes in the issue?<br>
&lt;dael> fantasai: Yes.<br>
&lt;dael> Rossen_: Obj to no change with clarification notes from the issue?<br>
&lt;dael> RESOLVED: no change with clarification notes from the issue<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2126#issuecomment-363963029 using your GitHub account
Received on Thursday, 8 February 2018 00:42:00 UTC

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