Intent to Ship: Imperative Shadow DOM Distribution API

[Yu Han]

Contact emails

yuzh...@chromium.org

Explainer

https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Imperative-Shadow-DOM-Distribution-API.md

Specification

https://github.com/whatwg/html/pull/5483, 

https://github.com/whatwg/dom/pull/860/

TAG review

https://github.com/w3ctag/design-reviews/issues/486

Summary

Web developers can specify node-to-slot assignments imperatively in Shadow DOM slotting. Please see the spec discussion [1] and the explainer [2]. 

[1] https://github.com/whatwg/html/issues/3534

[2] https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Imperative-Shadow-DOM-Distribution-API.md

Link to “Intent to Prototype” blink-dev discussion

https://groups.google.com/a/chromium.org/g/blink-dev/c/TNYIAu5E_M4/m/G10sAwwsAAAJ

Risks

Interoperability and Compatibility

The risk should be low because this is a new API. Comments from other implementers indicate their support of this feature.

Gecko: Positive (https://github.com/mozilla/standards-positions/issues/409)

WebKit: Positive (https://lists.webkit.org/pipermail/webkit-dev/2020-August/031318.html)

Web developers: Positive (https://github.com/whatwg/html/issues/3534#issuecomment-626258214)

Ergonomics

None. The interaction between imperative API and declarative API [1] has been discussed. And it has been resolved by allowing only one type of API under the same shadow root [2] . [1] https://github.com/whatwg/html/issues/3534#issuecomment-371024491 

[2] https://github.com/whatwg/html/issues/3534#issuecomment-537802687

Activation

The API is straightforward and feature detectable. Developers should be able to make use of it immediately without degrading the experience of users running older browsers.

Debuggability

No DevTools changes are required.

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?

Yes

Fully tested in WPT. 

https://wpt.fyi/results/shadow-dom/slots-imperative-slot-api.tentative.html?label=master&label=experimental&aligned 

https://wpt.fyi/results/shadow-dom/slots-imperative-api-slotchange.tentative.html?label=master&label=experimental&aligned

Tracking bug

http://crbug.com/869308

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5711021289242624

[Hayato Ito]

Non-owner LGTM. 

Super excited to see this moving forward!

--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABgHHk5LVtzjX5kGgoXbz_yCnAe7_mhmMJoL9hMRBMdacjOB5w%40mail.gmail.com.

--

Hayato

[Yu Han]

Thank you Hayato. 

I appreciate your insights and help in reviewing this project.

Han

[Chris Harrelson]

Hi, one comment below.

On Tue, Aug 11, 2020 at 12:32 PM 'Yu Han' via blink-dev <blin...@chromium.org> wrote:

Thank you Hayato. 

I appreciate your insights and help in reviewing this project.

Han

On Mon, Aug 10, 2020 at 11:19 PM Hayato Ito <hay...@chromium.org> wrote:

Non-owner LGTM. 

Super excited to see this moving forward!

On Tue, Aug 11, 2020 at 10:16 AM Yu Han <yuzh...@chromium.org> wrote:

Contact emails

yuzh...@chromium.org

Explainer

https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Imperative-Shadow-DOM-Distribution-API.md

Specification

https://github.com/whatwg/html/pull/5483, 

https://github.com/whatwg/dom/pull/860/

Are these pull requests blocked on anything other than final nits and LGTM, as far as you know? Since there is multi-vendor interest in this feature, we should be able to get those committed before shipping, which would be best.

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADkbBUuKBa8DrqdE%3Dg03mq_MPSRsrhffRV9aw56cY_Q9oE2FGg%40mail.gmail.com.

[Alex Russell]

LGTM1

Excited to see this moving forward.

[Mike West]

LGTM2.

[Yu Han]

Response inline.

On Thu, Aug 13, 2020 at 10:45 AM Chris Harrelson <chri...@chromium.org> wrote:

Hi, one comment below.

On Tue, Aug 11, 2020 at 12:32 PM 'Yu Han' via blink-dev <blin...@chromium.org> wrote:

Thank you Hayato. 

I appreciate your insights and help in reviewing this project.

Han

On Mon, Aug 10, 2020 at 11:19 PM Hayato Ito <hay...@chromium.org> wrote:

Non-owner LGTM. 

Super excited to see this moving forward!

On Tue, Aug 11, 2020 at 10:16 AM Yu Han <yuzh...@chromium.org> wrote:

Contact emails

yuzh...@chromium.org

Explainer

https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Imperative-Shadow-DOM-Distribution-API.md

Specification

https://github.com/whatwg/html/pull/5483, 

https://github.com/whatwg/dom/pull/860/

Are these pull requests blocked on anything other than final nits and LGTM, as far as you know? Since there is multi-vendor interest in this feature, we should be able to get those committed before shipping, which would be best.

Yes, as far as I know I've addressed all of the spec reviewer's concerns and waiting for a final review. Also, I used the requests re-review option a few weeks back, but haven't gotten a response.

I agree, it would be best to get those committed. However, I also think it's valuable to raise awareness to the web community via shipping status so more developers are inclined to try it out. 

[Chris Harrelson]

LGTM3

[Yu Han]

Thank you everyone!

Han