On Fri, Feb 2, 2024 at 9:37 AM Vladimir Levin <vmp...@google.com> 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 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 :) > I 100% agree. I have been trying to follow up <https://github.com/quilljs/quill/issues/3806#issuecomment-1886077331> with that team to see what the timeline looks like. But more importantly, I did my own testing and I can't see any negative effects on QuillJS pre-2.0 with Mutation Events disabled. So my hope is that even if the timeline doesn't line up, things might be "ok". That's another important thing: I've been running locally with Mutation Events disabled completely for about 4 months now, and I have yet to notice anything broken. That's anecdotal, but makes me feel a bit better that perhaps even if there is usage on a site, it might not be critical or noticable. 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.
