- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jul 2023 20:34:20 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-transforms-2] Syntax of individual transforms should reflect general CSS syntax`, and agreed to the following: * `RESOLVED: add the longhands to these properties as discussed above` <details><summary>The full IRC log of that discussion</summary> <florian> bramus: individual transforms property now exist, and help author with control over their animations<br> <florian> bramus: now people want more granularity, like translate-x, -y, etc<br> <florian> TabAtkins: I'm fine with that<br> <florian> TabAtkins: the other part was the logical transforms (translate-inline, etc)<br> <SebastianZ> q+<br> <astearns> ack fantasai<br> <florian> TabAtkins: that I'm against, because we don't have logical transforms, and thus nothing to map them too cleanly<br> <florian> bramus: that's ok<br> <florian> fantasai: do we want to just add those?<br> <flackr> q+<br> <astearns> ack SebastianZ<br> <florian> TabAtkins: that's part of this issue<br> <florian> SebastianZ: how about scale-x, scale-y, and the same for rorate<br> <florian> s/rorate/rotate/<br> <fantasai> s/that's/not/<br> <florian> TabAtkins: they were deliberately omitted from the transform properties, because there's no obvious correct order<br> <florian> TabAtkins: sorry, skew was omitted<br> <florian> flackr: does rotate has a long hand<br> <florian> TabAtkins: you'd have rotate-axis and rotate-angle<br> <astearns> ack flackr<br> <florian> flackr: when you create an animation with these now separate props, it might be surprising to authors:<br> <florian> flackr: if they set translate-x in the first and last keyframe, and -y in the middle, they'd only get the transition on the -<br> <florian> TabAtkins: that seems fine<br> <florian> fantasai: if you want the other behavior, then just put the necessary properties in the relevant keyframes<br> <florian> flackr: seems fine, never mind<br> <florian> bramus: the current standalone properties have enabled that, so it would be the same<br> <florian> TabAtkins: aminating on the separate properties and the joint ones give different results<br> <florian> astearns: Proposal: translate, rotate and scale have long hands<br> <flackr> q+<br> <florian> TabAtkins: translate -x and -y, rotate -angle -axis, scale -x -y -z<br> <TabAtkins> (and translate-z<br> <TabAtkins> )<br> <SebastianZ> q+<br> <astearns> ack flackr<br> <florian> flackr: is it well defined how we interpolate from one rotation angle to another<br> <florian> TabAtkins: I forget what the answer is, but yes, it's in the spec<br> <astearns> ack SebastianZ<br> <florian> SebastianZ: why rotate-angle and rotate-axis when we have rotate-x, rotate-y and rotate-z as functions<br> <florian> TabAtkins: there are multiple results depending on the order when you combine them, so it'd be ambiguous<br> <TabAtkins> TabAtkins: So if you do want to do independent rotations, use 'transform'<br> <florian> RESOLVED: add the longhands to these properties as discussed above<br> <astearns> ack fantasai<br> <Zakim> fantasai, you wanted to take up this comment as its own issue https://github.com/w3c/csswg-drafts/issues/7646#issuecomment-1545399874 which is filed at<br> <Zakim> ... https://github.com/w3c/csswg-drafts/issues/1544 already<br> <florian> dbaron: I'm not sure…<br> <florian> dbaron: I am concerned about the complexity this adds. Need to think about it.<br> <florian> astearns: how about you comment on the issue after reviewing that<br> <florian> fantasai: wanted to comment the logical part of this problem<br> <florian> astearns: it is a separate issue, and the agenda is already too crowded so no<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7646#issuecomment-1646210878 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 July 2023 20:34:22 UTC