As a developer, it's great to see Chrome implement full motion path functionality. However, in order to reduce unnecessary compatibility and potential issues, I hope that some CSSWG issues can be resolved before shipping
- Add "at <position>" to path(), shape(), and ray(): https://github.com/w3c/fxtf-drafts/issues/504#issuecomment-1466240729 - https://github.com/w3c/fxtf-drafts/issues/512 - https://github.com/w3c/csswg-drafts/issues/8828 在2023年5月11日星期四 UTC+8 20:38:31<sakh...@chromium.org> 写道： > Contact emailssakh...@chromium.org > > ExplainerAs part of the Interop 2023 we ship the rest of the CSS Motion > Path. Currently only path() works. And after a spec has been reworked other > path types are ready to be shipped. > > Specificationhttps://drafts.fxtf.org/motion > > Summary > > Motion path allows authors to position any graphical object and animate it > along an author specified path. This allows a number of powerful new > transform possibilities, such as positioning using polar coordinates (with > the ray() function) rather than the standard rectangular coordinates used > by the translate() function, or animating an element along a defined path, > making it easy to define complex and beautiful 2d spatial transitions. > Paths can be specified as circle(), ellipse(), rect(), inset(), xywh(), > polygon(), ray() and url(). > > Blink componentBlink>CSS > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> > > TAG reviewNone > > TAG review statusNot applicable > > Risks > > > Interoperability and Compatibility > > > *Gecko*: In development WIP as part of Interop 2023 > > *WebKit*: In development WIP as part of Interop 2023 > > *Web developers*: No signals > > *Other signals*: It's part of the Interop 2023 > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?Yes > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?Yes > https://wpt.fyi/results/css/motion > > Flag nameCSSOffsetPathBasicShapesCircleAndEllipse, > CSSOffsetPathBasicShapesRectanglesAndPolygon, CSSOffsetPathCoordBox, > CSSOffsetPathRay, CSSOffsetPathRayContain, CSSOffsetPathUrl > > Requires code in //chrome?False > > Estimated milestones > Shipping on desktop 115 > DevTrial on desktop 115 > Shipping on Android 115 > DevTrial on Android 115 > Shipping on WebView 115 > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5124394449371136 > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0094cd72-8e19-4244-af06-8b98f0c6224bn%40chromium.org.
