On Sat, May 13, 2023 at 1:09 AM Mike Taylor <miketa...@chromium.org> wrote:
> Hi Daniil, > On 5/11/23 8:38 AM, Daniil Sakhapov wrote: > > Contact emails sakha...@chromium.org > > Explainer As 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. > > Specification https://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 component Blink>CSS > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> > > TAG review None > > TAG review status Not applicable > > Any reason why? Has TAG ever reviewed the draft spec? > The feature has been shipping <https://developer.mozilla.org/en-US/docs/Web/CSS/offset-path#browser_compatibility> since Chrome 55 and Firefox 72, so it's already many years old. I don't think a high-level TAG review for this feature would make sense or be a good use of time. -- 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/CAARdPYfn46YbCf2R2VtrB%3DCG2ZtKp_DD0VyV0r6D91Nx9841Rw%40mail.gmail.com.
