Bug 139128 - Implement parsing of motion path properties
Summary: Implement parsing of motion path properties
Status: RESOLVED MOVED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 139127
  Show dependency treegraph
 
Reported: 2014-12-01 07:06 PST by Dirk Schulze
Modified: 2021-11-16 03:21 PST (History)
6 users (show)

See Also:


Attachments
[WIP] Parsing of the long hand properties (24.37 KB, patch)
2014-12-01 07:09 PST, Dirk Schulze
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Schulze 2014-12-01 07:06:20 PST
Implement parsing of motion path properties
Comment 1 Dirk Schulze 2014-12-01 07:09:45 PST
Created attachment 242308 [details]
[WIP] Parsing of the long hand properties

This is a WIP patch. I am currently unsure if I will be able to continue working on the patch. If someone wants to pick it up, feel welcome to do so.

* motion-position will be renamed to motion-distance
* motion-rotate is currently not implemented even though I added parts of it in the patch already.
* no compiler flag added yet
Comment 2 Dirk Schulze 2014-12-01 07:12:54 PST
(In reply to comment #1)
> Created attachment 242308 [details]
> [WIP] Parsing of the long hand properties
> 
> This is a WIP patch. I am currently unsure if I will be able to continue
> working on the patch. If someone wants to pick it up, feel welcome to do so.
> 
> * motion-position will be renamed to motion-distance
> * motion-rotate is currently not implemented even though I added parts of it
> in the patch already.
> * no compiler flag added yet

I forgot to add the Adobe copyright and to mention that parsing/style computation (including path() function) of motion-path is complete.
Comment 3 yisibl 2015-07-08 20:22:11 PDT
Chrome has supported.
Comment 4 Dirk Schulze 2016-10-12 05:12:00 PDT
Basic shapes parsing for path() got implemented (for clip-path) already. So it is just about implementing the properties now.
Comment 5 yisibl 2016-10-12 20:40:35 PDT
The CSS property names for Motion Path properties have changed.

Recent spec update:
https://drafts.fxtf.org/motion-1/
https://github.com/w3c/fxtf-drafts/pull/14

We have already shipped with the earlier names. For a period of time we can alias them to the new names.

motion-offset -> offset-distance
motion-path -> offset-path
motion-rotation -> offset-rotation
motion -> offset

See also:

https://bugs.chromium.org/p/chromium/issues/detail?id=637543
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/uqDmsIj6zJY/cS-Vp_XG2oYJ
Comment 6 Tobi Reif 2020-01-24 00:43:36 PST
Will offset-path be fully supported? eg as used in https://codepen.io/michellebarker/pen/XWJyydY (that demo doesn't work in Safari). Then this page https://caniuse.com/#search=offset-path should get updated.
Comment 7 Kiet Ho 2021-11-16 03:21:14 PST
Moved to 233109.