W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > April 2017

Re: [fxtf-drafts] [motion] offset-rotation should only do path-relative rotation

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Fri, 21 Apr 2017 06:16:02 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-296087644-1492755360-sysbot+gh@w3.org>
The CSS Working Group just discussed `https://github.com/w3c/fxtf-drafts/issues/69`, and agreed to the following resolutions:

* `RESOLVED: Close issue #69 no change.`

<details><summary>The full IRC log of that discussion</summary>

<shane> Topic: https://github.com/w3c/fxtf-drafts/issues/69
<shane> Github Topic: https://github.com/w3c/fxtf-drafts/issues/69
<TabAtkins> shane: First, issue was opened because you thought offset-rotation duplicated 'rotate'. I don't think that's true, and we should reject it.
<TabAtkins> shane: Second, this is a minor issue happening well after we shipped; we'd prefer to not make non-essential adjustments.
<fantasai> s/minor issue//
<TabAtkins> shane: Final output transform comes from several sources.
<TabAtkins> shane: offset, translate, rotate, scale, transform
<TabAtkins> shane: The order these happen in is quite integral to the result. Re-ordering is not generally possible.
<ericwilligers> https://drafts.csswg.org/css-transforms-2/#ctm
<TabAtkins> shane: So a rotation that happens in offset is different from one in TSR, which is different from one in transform.
<TabAtkins> shane: In particular, a rotate in "offset-*" rotates the frame of reference that the TSR properties work in.
<TabAtkins> fantasai: Do we *want* to do that?
<TabAtkins> shane: Yeah, definitely cases where you want to; you might be doing something independent in TRS.
<TabAtkins> fantasai: [describes some example she wants help with]
<TabAtkins> [something about additive properties not being possible yet]
<TabAtkins> [i believe the point is that the example in question is gonna need more control, probably in scripting, than we can reasonably provide in simple CSS anyway]
<fantasai> The use case is that you have the little motion path plan along its path, and then you want it to have an :active { /* shift it down/right by 2px to react to cick */ }
<fantasai> This should not require scripting
<TabAtkins> RESOLVED: Close issue #69 no change.

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/69#issuecomment-296087644 using your GitHub account
Received on Friday, 21 April 2017 06:16:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 November 2018 00:45:57 UTC