Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-07-11 Thread 'Noam Rosenthal' via blink-dev
Update on this: we're still interested in the next step but it's in the back burner until mutation event deprecation is complete, to avoid related noise. On Wednesday, April 3, 2024 at 12:52:23 PM UTC+1 Noam Rosenthal wrote: > On Tue, Apr 2, 2024 at 3:12 PM Aaron Leventhal > wrote: > >> A goo

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-04-03 Thread Noam Rosenthal
On Tue, Apr 2, 2024 at 3:12 PM Aaron Leventhal wrote: > A good start would be Scott O'Hara from Microsoft. He would know others to > loop in. > Thanks, will reach out. We see this deprecation as a long-haul thing, and sent this I2D to start the conversation. Thanks for the pointers! -- You rec

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-04-02 Thread 'Aaron Leventhal' via blink-dev
A good start would be Scott O'Hara from Microsoft. He would know others to loop in. On Tue, Apr 2, 2024 at 4:03 AM Yoav Weiss (@Shopify) wrote: > Hmm, would it make sense then to work with the accessibility community to > get them to move to mutation observers before attempting to remove here? >

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-04-02 Thread Yoav Weiss (@Shopify)
Hmm, would it make sense then to work with the accessibility community to get them to move to mutation observers before attempting to remove here? Do we know folks with contacts in these circles? ^^ +Aaron Leventhal On Fri, Mar 29, 2024 at 7:01 PM Ian Kilpatrick wrote: > > > On Fri, Mar 29, 20

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-03-29 Thread Ian Kilpatrick
On Fri, Mar 29, 2024 at 4:33 AM Noam Rosenthal wrote: > > > On Fri, Mar 29, 2024 at 6:33 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> On top of Domenic's questions, have we tried to estimate the risk here? >> Even if it's Chromium-only, there could be Enterprise or embedded sc

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-03-29 Thread Noam Rosenthal
On Fri, Mar 29, 2024 at 6:33 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > On top of Domenic's questions, have we tried to estimate the risk here? > Even if it's Chromium-only, there could be Enterprise or embedded scenarios > that somehow rely on it. > Yes, and we're willing to keep

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-03-28 Thread Yoav Weiss (@Shopify)
On top of Domenic's questions, have we tried to estimate the risk here? Even if it's Chromium-only, there could be Enterprise or embedded scenarios that somehow rely on it. Do we know how often this blur event actually fires? On Fri, Mar 29, 2024 at 5:28 AM Domenic Denicola wrote: > > > On Fri,

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-03-28 Thread Domenic Denicola
On Fri, Mar 29, 2024 at 2:33 AM Noam Rosenthal wrote: > Contact emailsnrosent...@chromium.org, d...@chromium.org > > ExplainerNone > A few paragraphs, including e.g. example code and how it behaves differently before/after the change, would help clarify this for web developers. > > > Specifica

[blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

2024-03-28 Thread Noam Rosenthal
Contact emailsnrosent...@chromium.org, d...@chromium.org ExplainerNone Specificationhttps://html.spec.whatwg.org/#dom-trees:event-blur Summary Currently Chromium-based browsers are the only ones that fire blur events when an element is removed from the DOM. This has recently been clarified in t