Re: [whatwg/dom] Declarative Shadow DOM (#831)

I've updated the [explainer](https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md) with various things from this discussion:
- Cleaned up the "Behavior" section, to hopefully get it a bit closer to spec language.
- Added the new `getInnerHTML()` function to take the place of needing to opt-in to `innerHTML` serialization during `attachShadow()`.
- Added shadowroot_delegates_focus (and similar) attributes to the declarative `<template>` form.
- Added a comment about CSS custom states and AOM IDL attributes from @justinfagnani.
- Per @rniwa, I re-ran the performance section with the template.content.cloneNode() call removed. I also added another "script at the end" snippet, and used [tachometer](https://www.npmjs.com/package/tachometer) for better timing. TL/DR: the inline script approach is still ~5x slower, and the "script at the end" approach is 10% slower.
- Changed the polyfill example to the @Rich-Harris Clock, which gives a better idea of how hydration might work. As mentioned above, this is just an illustration.

I have sent a [Chromium Intent to Prototype](https://groups.google.com/a/chromium.org/d/msg/blink-dev/nJDc-1s3R9U/uCJKsEqpAwAJ) for this feature, and it is available in basic form behind the `DeclarativeShadowDOM` runtime feature (or chrome://flags/#enable-experimental-web-platform-features). It is still very much in development, but if you find an interesting bug, please feel free to [report it](https://bugs.chromium.org/p/chromium/issues/entry?components=Blink%3EDOM%3EShadowDOM&labels=pri-2,type-bug).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/831#issuecomment-594776039