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:
>>>
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
>>
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
>
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
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
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
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
