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 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 request for deprecation thread: https://groups.google.com/a/chromium.org/g/blink-dev/c/qDsKRU-cQ_4/m/P_iXWapTBgAJ And I’ll send a request for removal closer to 126. Thanks, Mason > On Tue, Feb 6, 2024 at 5:12 PM Mason Freed <mas...@chromium.org> wrote: > >> >> >> On Tue, Feb 6, 2024 at 3:38 AM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> 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 be broken. I can’t see any breakage myself. >> >> What would breakage look like? Are we expecting JS to be borked entirely? >>>> Or do we expect the events to stop firing, resulting in hopefully smaller >>>> and less-visible breakage? >>>> >>> >> No there shouldn’t be any exceptions thrown, so the JS should be fine. >> It’s just that those events will not be fired. The breakage, whatever it >> is, is so small that I’ve yet been able to notice it. That’s not to say >> there isn’t risk - there surely is. Just that I’m hopeful. >> >> Thanks, >> Mason >> >> >> >>>> >>>> >>>> >>>>> >>>>>> >>>>>>> The npm package you listed, for example, would use the actual >>>>>>> events if available, so sites using that polyfill would also count >>>>>>> towards >>>>>>> the event usage if the browser supports those even though that's "safe", >>>>>>> right? >>>>>>> >>>>>> >>>>>> This is an excellent point that I hadn't thought of. I'm going to >>>>>> modify the polyfill right now to *always* run. That way polyfilled usage >>>>>> will no longer be counted. I'm used to writing polyfills for features >>>>>> that >>>>>> are getting *added*, where you want to avoid using the polyfill when the >>>>>> feature is supported. This is the opposite. >>>>>> >>>>>> Thanks, >>>>>> Mason >>>>>> >>>>>> >>>>>> >>>>>>>> >>>>>>>> *Gecko*: Positive ( >>>>>>>> https://github.com/mozilla/standards-positions/issues/807) "very >>>>>>>> strong positive position" >>>>>>>> >>>>>>>> *WebKit*: No signal ( >>>>>>>> https://github.com/WebKit/standards-positions/issues/192) >>>>>>>> >>>>>>>> *Web developers*: No signals >>>>>>>> >>>>>>>> *Other signals*: >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> Goals for experimentation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Ongoing technical constraints >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Debuggability >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>>>>> Mac, Linux, ChromeOS, Android, and Android WebView)?Yes >>>>>>>> >>>>>>>> Is this feature fully tested by web-platform-tests >>>>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>>>>> ?No >>>>>>>> >>>>>>>> Flag name on chrome://flags >>>>>>>> >>>>>>>> Finch feature nameNone >>>>>>>> >>>>>>>> Non-finch justificationNone >>>>>>>> >>>>>>>> Requires code in //chrome?False >>>>>>>> >>>>>>>> Tracking bughttps://crbug.com/1446498 >>>>>>>> >>>>>>>> Estimated milestones >>>>>>>> Shipping on desktop 115 >>>>>>>> OriginTrial desktop last 134 >>>>>>>> OriginTrial desktop first 124 >>>>>>>> Shipping on Android 115 >>>>>>>> OriginTrial Android last 134 >>>>>>>> OriginTrial Android first 124 >>>>>>>> Shipping on WebView 115 >>>>>>>> OriginTrial webView last 134 >>>>>>>> OriginTrial webView first 124 >>>>>>>> >>>>>>>> Link to entry on the Chrome Platform Status >>>>>>>> https://chromestatus.com/feature/5083947249172480 >>>>>>>> >>>>>>>> Links to previous Intent discussionsIntent to Experiment: >>>>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/qDsKRU-cQ_4/m/isA1mZ_aAAAJ >>>>>>>> >>>>>>>> >>>>>>>> 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/CAM%3DNeDjevtANjMn1NUK83UGyJyv4HrLCFkjs9fhL6UVov_uAkA%40mail.gmail.com >>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjevtANjMn1NUK83UGyJyv4HrLCFkjs9fhL6UVov_uAkA%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/CAM%3DNeDgpfzo%3DztS_MEzJg7N4vgiNXR2D-CcBwvZp9KaX_W0MyA%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDgpfzo%3DztS_MEzJg7N4vgiNXR2D-CcBwvZp9KaX_W0MyA%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/CAM%3DNeDh6uyQOCtj7s5ffMJ5qmreW2a%2B3wDR22KCw_OSM2FtoVA%40mail.gmail.com.
