Re: [blink-dev] Intent to Ship: CSS Motion Path

[Yoav Weiss]

LGTM3

On Wed, May 24, 2023 at 5:55 PM Alex Russell 
wrote:

> LGTM2; looking forward to this launching.
>
> On Wednesday, May 24, 2023 at 8:55:07 AM UTC-7 Rick Byers wrote:
>
>> LGTM1
>>
>> On Tue, May 16, 2023 at 9:03 AM Daniil Sakhapov 
>> wrote:
>>
>>> Issued the requests:
>>> https://github.com/WebKit/standards-positions/issues/187 and
>>> https://github.com/mozilla/standards-positions/issues/802.
>>>
>>> Also note: the spec has been largely finalised, so I don't expect any
>>> big changes, including the issues mentioned by 一丝.
>>> On Tuesday, May 16, 2023 at 1:39:21 PM UTC+2 Philip Jägenstedt wrote:
>>>
 On Sat, May 13, 2023 at 1:09 AM Mike Taylor 
 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
> 
>
> TAG review None
>
> TAG review status Not applicable
>
> Any reason why? Has TAG ever reviewed the draft spec?
>

 The feature has been shipping
 
 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/411f1518-8153-480d-ae23-194bc866c92an%40chromium.org
>>> 
>>> .
>>>
>> --
> 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/e78437a3-5079-46b9-9759-032fa9f67148n%40chromium.org
> 
> .
>

-- 
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/CAL5BFfVb-md%2Bw_uoyvv4UZ2Et-2dbZLHAp9c1c1uS1JVgRaQxQ%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: CSS Motion Path

[Alex Russell]

LGTM2; looking forward to this launching.

On Wednesday, May 24, 2023 at 8:55:07 AM UTC-7 Rick Byers wrote:

> LGTM1
>
> On Tue, May 16, 2023 at 9:03 AM Daniil Sakhapov  
> wrote:
>
>> Issued the requests: 
>> https://github.com/WebKit/standards-positions/issues/187 and 
>> https://github.com/mozilla/standards-positions/issues/802.
>>
>> Also note: the spec has been largely finalised, so I don't expect any big 
>> changes, including the issues mentioned by 一丝. 
>> On Tuesday, May 16, 2023 at 1:39:21 PM UTC+2 Philip Jägenstedt wrote:
>>
>>> On Sat, May 13, 2023 at 1:09 AM Mike Taylor  
>>> 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 
 

 TAG review None

 TAG review status Not applicable

 Any reason why? Has TAG ever reviewed the draft spec?

>>>
>>> The feature has been shipping 
>>> 
>>>  
>>> 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/411f1518-8153-480d-ae23-194bc866c92an%40chromium.org
>>  
>> 
>> .
>>
>

-- 
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/e78437a3-5079-46b9-9759-032fa9f67148n%40chromium.org.

Re: [blink-dev] Intent to Ship: CSS Motion Path

[Rick Byers]

LGTM1

On Tue, May 16, 2023 at 9:03 AM Daniil Sakhapov 
wrote:

> Issued the requests:
> https://github.com/WebKit/standards-positions/issues/187 and
> https://github.com/mozilla/standards-positions/issues/802.
>
> Also note: the spec has been largely finalised, so I don't expect any big
> changes, including the issues mentioned by 一丝.
> On Tuesday, May 16, 2023 at 1:39:21 PM UTC+2 Philip Jägenstedt wrote:
>
>> On Sat, May 13, 2023 at 1:09 AM Mike Taylor 
>> 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
>>> 
>>>
>>> TAG review None
>>>
>>> TAG review status Not applicable
>>>
>>> Any reason why? Has TAG ever reviewed the draft spec?
>>>
>>
>> The feature has been shipping
>> 
>> 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/411f1518-8153-480d-ae23-194bc866c92an%40chromium.org
> 
> .
>

-- 
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/CAFUtAY9Rrpw386wh-xRVn%2BE_z20xRAHMD5McHvXk-n60S6NuwQ%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: CSS Motion Path

[Daniil Sakhapov]

Issued the 
requests: https://github.com/WebKit/standards-positions/issues/187 
and https://github.com/mozilla/standards-positions/issues/802.

Also note: the spec has been largely finalised, so I don't expect any big 
changes, including the issues mentioned by 一丝. 
On Tuesday, May 16, 2023 at 1:39:21 PM UTC+2 Philip Jägenstedt wrote:

> On Sat, May 13, 2023 at 1:09 AM Mike Taylor  
> 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 
>> 
>>
>> TAG review None
>>
>> TAG review status Not applicable
>>
>> Any reason why? Has TAG ever reviewed the draft spec?
>>
>
> The feature has been shipping 
> 
>  
> 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/411f1518-8153-480d-ae23-194bc866c92an%40chromium.org.

Re: [blink-dev] Intent to Ship: CSS Motion Path

[Philip Jägenstedt]

On Sat, May 13, 2023 at 1:09 AM Mike Taylor  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
> 
>
> TAG review None
>
> TAG review status Not applicable
>
> Any reason why? Has TAG ever reviewed the draft spec?
>

The feature has been shipping

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.

Re: [blink-dev] Intent to Ship: CSS Motion Path

[Mike Taylor]

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 




TAG review

None


TAG review status

Not applicable

Any reason why? Has TAG ever reviewed the draft spec?



Risks



Interoperability and Compatibility


/Gecko/: In development WIP as part of Interop 2023

/WebKit/: In development WIP as part of Interop 2023
Per 
https://groups.google.com/a/chromium.org/g/blink-dev/c/HxqAcgnTs8o/m/I_Fx6FoRBQAJ, 
can we request formal signals from Apple and Mozilla?


/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

?

Yes
https://wpt.fyi/results/css/motion


Flag name

CSSOffsetPathBasicShapesCircleAndEllipse, 
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 
.

--
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/CAH3Z92-4tVqmp5E_4ScWLqgmfdV0abMf_eoVrPrP76pLsBz2Fg%40mail.gmail.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/40f718e6-6252-af91-9be8-0a0f30444961%40chromium.org.

[blink-dev] Intent to Ship: CSS Motion Path

[Daniil Sakhapov]

Contact emailssakha...@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


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

?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
.

-- 
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/CAH3Z92-4tVqmp5E_4ScWLqgmfdV0abMf_eoVrPrP76pLsBz2Fg%40mail.gmail.com.