On 2024-02-17 03:22, Mason Freed wrote:
On Sat, Feb 10, 2024 at 5:39 AM Daniel Bratell
wrote:
Just thinking about possible use cases for mutation events, do you
know what the browser extension situation is? Those might have
legitimate reason to react to page changes and maybe
On Sat, Feb 10, 2024 at 5:39 AM Daniel Bratell wrote:
> Just thinking about possible use cases for mutation events, do you know
> what the browser extension situation is? Those might have legitimate reason
> to react to page changes and maybe some of them use the old events?
>
> That's a good
Just thinking about possible use cases for mutation events, do you know
what the browser extension situation is? Those might have legitimate
reason to react to page changes and maybe some of them use the old events?
/Daniel
On 2024-02-09 21:35, Mason Freed wrote:
On Wed, Feb 7, 2024 at 6:52
On Wed, Feb 7, 2024 at 6:52 AM Yoav Weiss (@Shopify)
wrote:
> LGTM to run a deprecation trial M124-M134 inclusive.
>
Thanks!
>
> May our mutations no longer be eventful!!
>
> On Wed, Feb 7, 2024 at 3:50 PM Mason Freed wrote:
>
>>
>>
>> On Wed, Feb 7, 2024 at 6:06 AM Yoav Weiss (@Shopify)
LGTM to run a deprecation trial M124-M134 inclusive.
May our mutations no longer be eventful!!
On Wed, Feb 7, 2024 at 3:50 PM Mason Freed wrote:
>
>
> On Wed, Feb 7, 2024 at 6:06 AM Yoav Weiss (@Shopify) <
> yoavwe...@chromium.org> wrote:
>
>> Just to clarify - this intent is asking to start a
On Wed, Feb 7, 2024 at 6:06 AM Yoav Weiss (@Shopify)
wrote:
> Just to clarify - this intent is asking to start a deprecation trial for
> mutation events in 124 and ending it in 134, but you'd send a separate
> intent on the actual removal of mutation events?
>
Yes, that’s correct. Here’s the
Just to clarify - this intent is asking to start a deprecation trial for
mutation events in 124 and ending it in 134, but you'd send a separate
intent on the actual removal of mutation events?
On Tue, Feb 6, 2024 at 5:12 PM Mason Freed wrote:
>
>
> On Tue, Feb 6, 2024 at 3:38 AM Yoav Weiss
On Tue, Feb 6, 2024 at 3:38 AM Yoav Weiss (@Shopify)
wrote:
>
> Note that them shipping 2.0 and everyone upgrading to 2.0 are not the same
> thing, and is unlikely to happen at the same time..
>
Agreed for sure. That’s why I’ve been trying to get them to confirm exactly
what functionality will
On Fri, Feb 2, 2024 at 7:37 PM Mason Freed wrote:
> On Fri, Feb 2, 2024 at 9:37 AM Vladimir Levin wrote:
>
>> It's good to know that QuillJS seems to be addressing their issue in 2.0,
>> although the currently published stable version is still 1.x. I just wanted
>> to verify the timeline for
On Fri, Feb 2, 2024 at 9:37 AM Vladimir Levin wrote:
> It's good to know that QuillJS seems to be addressing their issue in 2.0,
> although the currently published stable version is still 1.x. I just wanted
> to verify the timeline for disabling these features. The trial is for
> 124-134 and the
On Thu, Feb 1, 2024 at 6:30 PM Mason Freed wrote:
>
> On Thu, Feb 1, 2024 at 7:12 AM Vladimir Levin wrote:
>
>> This is very exciting! Thank you for working on this.
>>
>
> Thanks!
>
>
>> Do you know whether the existing usage is feature checked? 1.58% seems
>> very high, but if it's feature
On Thu, Feb 1, 2024 at 7:12 AM Vladimir Levin wrote:
> This is very exciting! Thank you for working on this.
>
Thanks!
> Do you know whether the existing usage is feature checked? 1.58% seems
> very high, but if it's feature checked and fallback is something like
> mutation observer, then it
On Wed, Jan 31, 2024 at 8:54 PM Mason Freed wrote:
> Contact emailsmas...@chromium.org
>
> ExplainerNone
>
> Specificationhttps://w3c.github.io/uievents/#legacy-event-types
>
> Summary
>
> Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`,
> `DOMNodeRemoved`,
Contact emailsmas...@chromium.org
ExplainerNone
Specificationhttps://w3c.github.io/uievents/#legacy-event-types
Summary
Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`,
`DOMNodeRemoved`, `DOMNodeRemovedFromDocument`,
`DOMNodeInsertedIntoDocument`, and
14 matches
Mail list logo
