On Wed, Feb 15, 2023 at 10:14 PM Yoav Weiss <yoavwe...@chromium.org> wrote:
> Do you have any predicted end milestone for the deprecation? What does > current usage look like? > So usage has ticked up recently, to about 0.01% <https://chromestatus.com/metrics/feature/timeline/popularity/3196>. I think the spike is due to recent interest from other implementers, and the coming standardization of this feature. However, I expect that usage to migrate to the new attribute fairly quickly, since it is likely made up of early adopters that are keeping up to date with this feature. Having said that, I don't know how long it'll take. I would not be surprised if it takes until the end of the year for usage to be low enough that it isn't concerning. That would put it around M122 or so. I know this isn't concrete, but let me know if it answers your question! Thanks, Mason > > +Jason Robbins <jrobb...@google.com> - FYI, this didn't make it to the > chromestatus tool. > > On Sat, Feb 11, 2023 at 2:04 AM Mason Freed <mas...@chromium.org> wrote: > >> Contact emailsmas...@chromium.org >> >> ExplainerNone >> >> Specificationhttps://github.com/whatwg/html/pull/5465 >> >> Summary >> >> The standards-track `shadowrootmode` attribute, which enables declarative >> Shadow DOM, was shipped in Chrome 111 >> <https://chromestatus.com/feature/5161240576393216>. The older, >> non-standard `shadowroot` attribute is now deprecated. During the >> deprecation period, both attributes are functional, however the >> `shadowroot` attribute does not enable the new streaming behavior, whereas >> `shadowrootmode` allows streaming of content. There is a straightforward >> migration path: replace `shadowroot` with `shadowrootmode`. >> >> >> Blink componentBlink>DOM>ShadowDOM >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDOM%3EShadowDOM> >> >> Search tagsdeclarative >> <https://chromestatus.com/features#tags:declarative>, shadow >> <https://chromestatus.com/features#tags:shadow>, dom >> <https://chromestatus.com/features#tags:dom>, shadowroot >> <https://chromestatus.com/features#tags:shadowroot> >> >> TAG review >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> The current (2-10-23) usage of `shadowroot` is 0.01% [1], which is >> relatively high. The hope is that as developers learn about the >> now-standardized `shadowrootmode` attribute, and understand that it: 1. >> supports streaming (which is preferred), and 2. is standardized, and should >> appear soon in other browsers ...they will naturally migrate away from the >> `shadowroot` attribute, and usage will drop. We will continue to monitor >> the usage and will only attempt to remove the old attribute's functionality >> when usage is sufficiently small. With this deprecation, a warning will >> appear in the DevTools issues pane, which should help with developer >> education. [1] >> https://chromestatus.com/metrics/feature/timeline/popularity/3196 >> >> >> *Gecko*: No signal >> >> *WebKit*: No signal >> >> *Web developers*: No signals >> >> *Other signals*: >> >> Activation >> >> Developer outreach will be important, to educate developers about the new >> `shadowrootmode` attribute and behavior. >> >> >> Security >> >> Not really applicable to this deprecation, but the security/XSS issues >> that applied to `shadowroot` also apply to `shadowrootmode`. See >> https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md#security-and-privacy-considerations. >> I do not think this deprecation affects that issue. >> >> >> 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? >> >> >> >> Debuggability >> >> N/A >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, 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> >> ?Yes >> >> Flag name >> >> Requires code in //chrome?False >> >> Tracking bughttps://crbug.com/1396384 >> >> Estimated milestones >> DevTrial on desktop 112 >> DevTrial on Android 112 >> >> Anticipated spec changes >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/6239658726391808 >> >> 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%3DNeDhn62d2CEDggcQW0qW4EUiTX9GmMkesQp-1dPd4uRXndA%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDhn62d2CEDggcQW0qW4EUiTX9GmMkesQp-1dPd4uRXndA%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%3DNeDgJa3ThqVR-kU3uUSyvcwzYvT%3Drsywj5RhXnHaKsuW%3D_w%40mail.gmail.com.
