Issue metadata
Sign in to add a comment
|
CSS: New names for motion path properties |
||||||||||||||||||||||||||||||||||||||||||||
Issue descriptionChange description: The motion-* property names have been replaced with offset-* The old names become deprecated, to be removed. Changes to API surface: motion-path becomes offset-path motion-offset becomes offset-distance motion-rotation becomes offset-rotation motion becomes offset Links: Spec: https://drafts.fxtf.org/motion-1/ Public standards discussion: CSSWG action: https://www.w3.org/Style/CSS/Tracker/actions/781 Merged pull request: https://github.com/w3c/fxtf-drafts/pull/14 Support in other browsers: No other browsers support Motion Path yet.
,
Oct 10 2016
,
Oct 11 2016
,
Oct 11 2016
Eric, Can you please put the right version number on the chrome status entry? https://www.chromestatus.com/features/6390764217040896 Thanks, Joe Joe Medley | Technical Writer, Chrome DevRel | jmedley@google.com | 816-678-7195 *If an API's not documented it doesn't exist.*
,
Oct 12 2016
> Can you please put the right version number on the chrome status entry? > https://www.chromestatus.com/features/6390764217040896 Done
,
Feb 24 2017
M58 is branching next week and there are some deprecation messages linked to this work, for M58. Are we on track for removal or do we need to edit the target milestone?
,
Feb 24 2017
Ok for removal. We should mention in the blog that authors should use offset-path instead. |
|||||||||||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||||||||||||||
Comment 1 by suzyh@chromium.org
, Oct 10 2016