The editors' draft specification is available at http://dev.w3.org/fxtf/motion-1/ Motion paths allow authors to animate elements along an author-specified path. Motion path animation provides an easy way for authors to declaratively specify animation of an element along a sequence of lines, arcs or splines. This is a CSS equivalent to the animateMotion tag, but for all HTML and SVG elements. (animateMotion only works with SVG elements, and only in browsers that support SMIL.) The following CSS properties are implemented and proposed for shipping: motion-path: none | path(<string>) motion-offset: <length> | <percentage> motion-rotation: [ auto | reverse ] && <angle> motion: <motion-path> && <motion-offset> && <motion-rotation> When the motion-offset property is animated, for example using Web Animations, the element moves along the path. When motion-rotation is 'auto' (the default), the element automatically rotates as it follows the path. The following motion-path options from the spec are not implemented or proposing for shipping at this time: <url> , <basic-shape> , <geometry-box> , path <fill-rule>
@Astley Chen Are you going to support this feature?
(In reply to percyley from comment #2) > @Astley Chen Are you going to support this feature? It's under consideration now, would you like to share your thoughts against the spec stability and current support level of browsers ? Your feedback is welcome.
Chrome 46+ and Opera 33+ support this, but not fully supported. They only support motion-path: none|path(). See https://bug1186329.bmoattachments.org/attachment.cgi?id=8753754 I think the next CSS specification will have more SVG features, developers are also very much look forward to these characteristics, such as the recent mozilla implementation of the background-clip: text.
There were significant changes to this specification agreed at the CSS working group's face-to-face meeting last week, to merge this specification with the polar positioning feature in CSS round display. We should wait until those changes shake out before working on an implementation here.
The specification has now been greatly changed: motion-offset -> offset-distance motion-path -> offset-path motion-rotation -> offset-rotation motion -> offset Add: offset-position offset-anchor offset-path(motion-path) add <angle> and <size> Chrome has fully implemented the new specification: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/o1C5NzGf9Q0/sbaLF1MbAgAJ