8 replies

1. jerry 1 min later

   @zachleat the shadowroot attribute got deprecated in favor of shadowrootmode.

   "Summary
   The standards-track `shadowrootmode` attribute, which enables declarative Shadow DOM, was shipped in Chrome 111. 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`."

   https://botsin.space/@intenttoship/109843427498199155

   1. Jared White (ResistanceNet ✊) 13 min later

      @jerryD @zachleat Right, both Chrome and Safari are now moving forward with shadowrootmode alongside shadowroot in Chrome being sunsetted.

   2. Zach Leatherman 22 min later

      @jerryD a ha, thank you!

2. Danny Blue 9 min later

   @zachleat they changed the behavior to attach the shadow root after the opening tag so that streaming would work. Part of that change also changed the attribute name.

   1. Zach Leatherman 31 min later

      @deebloo thank you!

      1. Danny Blue 43 min later

         @zachleat yeah we will have a few years of running dsd in "chrome compat mode" lol

3. Zach Leatherman 22 min later

   Here’s the context from @jerryD (thank you!)

   https://techhub.social/@jerryD/109876616115187403

4. ryan 2 hr later

   @zachleat I was equally baffled by this a few days ago and I ended up finding the exact GitHub issue thread where this was discussed: https://github.com/whatwg/html/pull/5465#discussion_r1004046952

   I think one of the core issues was that `HTMLTemplateElement.shadowRoot` + the `shadowroot` attribute conflicted with the existence of `Element.shadowRoot`. On template elements it would have been a `string` but everywhere else it could have been a reference to an actual shadow root, which is pretty confusing!