On Thu, Feb 1, 2024 at 6:30 PM Mason Freed <mas...@chromium.org> wrote:
> > On Thu, Feb 1, 2024 at 7:12 AM Vladimir Levin <vmp...@google.com> 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 would be a lot more safe imho. Also, do you have >> a sense of where the usage is coming from (a few large frameworks vs a ton >> of smaller sites)? >> > > Unfortunately, I haven't seen a lot of feature checking around mutation > events directly. I have definitely seen feature checks on MutationObserver > that then avoids trying to use mutation events. But obviously those aren't > part of the use counter data, since they don't attach mutation > event listeners. > > I've been looking into UKM data to see if I can suss out any large usage > patterns. I've found a few, e.g. QuillJS > <https://github.com/quilljs/quill/issues/3806>, which contribute a > significant chunk of usage to many sites. Thankfully in the cases I've > seen, the (large) deprecation warnings I've added to Chrome seem to be doing > their thing > <https://github.com/quilljs/quill/issues?q=is%3Aissue+deprecated++mutation>. > My hope is that direct outreach (which I've done in a few cases), heavy > warnings, and eventually the start of the removal effort (plus this OT to > give sites an extension) will nudge the remaining users to migrate. > 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 feature will be turned off by default in 127. Sounds reasonable to me, but I'd encourage checking whether QuillJS ships to 2.0 in the 127 timeframe :) > >> 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/CADsXd2NxRiqpMZQ6op_WSwaDHzhax5NEVxF%3D12S8onmTwLCgGg%40mail.gmail.com.
