- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Nov 2019 17:57:17 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `The readiness of shipping individual transform properties - translate, rotate, scale`, and agreed to the following: * `RESOLVED: Working group is fine with translate, rotate and scale shipping` * `RESOLVED: Move the 3D transforms to a level 3of Transforms` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: The readiness of shipping individual transform properties - translate, rotate, scale<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4515<br> <dael> astearns: Gecko is ready to ship. Any concerns about that?<br> <fantasai> I would like us to get the spec to CR soonish<br> <fantasai> would it make sense to drop the 3D Transforms section to L3<br> <fantasai> ?<br> <fantasai> and then make L2 be 2D transforms + this feature?<br> <dael> astearns: [reads fantasai IRC] should we drap 3d transforms for that?<br> <dael> s/drap/drop<br> <fantasai> Just push to level three<br> <dael> smfr: Tranforms 1.5 which is 1+individual functions<br> <fantasai> then L3 is about 3D, even :)<br> <dael> TabAtkins: I'm fine with punting items to L3<br> <fantasai> super better<br> <fantasai> than L1.5<br> <fantasai> :)<br> <dael> astearns: Anothor impl of individual functions soon?<br> <fantasai> we're not in CR yet, so it's about the spec, not impl status<br> <dael> fremy: I think they were behind a flag in old Edge<br> <fantasai> if spec for individual functions is done, let's push it to CR and defer the rest to L3<br> <dael> astearns: I wouldn't mind moving the 3D transforms. Wondering what other small things will drop to L3.<br> <dael> fremy: Old Edge has a flag to enable individual transforms. So we have impl to move the spec forward<br> <fantasai> Propose several resolutions<br> <fantasai> First resolution, clear these to ship<br> <dael> smfr: Interaction with motion path I'm forgetting about?<br> <fantasai> 2nd resolution, push everything other than these features (unless someone thinks there's something else close to CR) to L3<br> <dael> astearns: Can anyone answer that yes or no?<br> <fantasai> I don't think so<br> <dael> emilio: Motion path adds transform-ish stuff but the order is well defined.<br> <dael> myles: There's an order. Apply transform properties and then motion path. Might have it flipped, but it's well defined. No interaction<br> <dael> astearns: First proposed resolution is clear these to ship<br> <dael> astearns: Not hearing concerns. Objections to Working group is fine with translate, rotate and scale shipping?<br> <dael> RESOLVED: Working group is fine with translate, rotate and scale shipping<br> <myles> emilio<br> <dael> astearns: 2nd is move the 3d transforms out to a new level. ANy concerns?<br> <TabAtkins> Yeah, the total effective transform is <motion-path> <translate> <rotate> <scale> <transform><br> <emilio> myles: np! :)<br> <TabAtkins> (with perspective/transform-origin bodged into the <transform> bit there)<br> <dael> RESOLVED: Move the 3D transforms to a level 3of Transforms<br> <dael> astearns: I think we should take it up in a call soon about taking L2 Transforms to CR<br> <TabAtkins> Or wait, dbaron's right, transform-origin goes before <translate> and after <transform><br> <dael> astearns: I don't think that's something for 4 minutes<br> <fantasai> probably need to wait for edits :)<br> <fantasai> also maybe republish both as WD/FPWD<br> <dael> astearns: IRC question about transform-origin?<br> <dbaron> also perspective is a little bit fun<br> <dael> TabAtkins: No, just chatting about effect, but it's well understood<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4515#issuecomment-556175448 using your GitHub account
Received on Wednesday, 20 November 2019 17:57:19 UTC