On Fri, Mar 29, 2024 at 2:33 AM Noam Rosenthal <nrosent...@chromium.org> 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. > > > 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 the spec. As part of an effort to reduce synchronous side-effects of DOM > insertion & removal, this deprecation will cautiously test the impact and > feasibility of aligning with the spec/other browsers on this. > > > Blink componentBlink>DOM > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDOM> > > TAG reviewNone > > TAG review statusNot applicable > > Risks > > > Interoperability and Compatibility > > None > > > *Gecko*: Shipped/Shipping > > *WebKit*: Shipped/Shipping > > *Web developers*: No signals > > *Other signals*: > > Ergonomics > > There is no new API here, only a change to an existing behavior. > > > Activation > > N/A > > > Security > > Shouldn't be applicable. > > > 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? > > None > > > Debuggability > > None > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?Yes > > > https://wpt.fyi/results/dom/nodes/insertion-removing-steps/blur-event.window.html?label=experimental&label=master&aligned > > > Flag name on chrome://flagsOmitBlurEventOnElementRemoval > > Finch feature nameOmitBlurEventOnElementRemoval > > Requires code in //chrome?False > > Tracking bughttps://g-issues.chromium.org/issues/41484175 > > Estimated milestones > > No milestones specified > Can you specify what milestones you are planning to deprecate for, and what milestone you are planning to remove in? > > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5128696823545856?gate=5183419526152192 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.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/CAJn%3DMYZqb%2BD4BEuaK4HzAAy7Td6QvJZhhOuWGH3a9SHyGKMUyQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZqb%2BD4BEuaK4HzAAy7Td6QvJZhhOuWGH3a9SHyGKMUyQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAM0wra9a5fLM%3DSiOkq0xmrovf2ZANwDncBQjO0BKWvoxzFQNJg%40mail.gmail.com.
