Re: [w3c/webcomponents] Expose shadowRoot on element internals (#871) from Darien Maillet Valentine on 2020-08-18 (public-webapps-github@w3.org from August 2020)

From: Darien Maillet Valentine <notifications@github.com>
Date: Tue, 18 Aug 2020 16:20:34 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/871/675766026@github.com>

> That discussion bikesheds for a while on naming before petering out without a conclusion, here. And the API is implemented without an opt-in or opt-out. 

Isn’t the opt-out specified already in HTML, though?

![steps 14, 6 through 14, 10 of the element definition algorithm](https://user-images.githubusercontent.com/6257356/90574519-2113c600-e187-11ea-8018-225c06cf5a8c.png)

(https://html.spec.whatwg.org/multipage/custom-elements.html#element-definition in step 14)

In Chrome (86.0.4235.0) this appears to work:

![screenshot showing Chrome console respecting the opt-out API](https://user-images.githubusercontent.com/6257356/90574745-b2833800-e187-11ea-96e0-63a41b14e4ca.png)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/871#issuecomment-675766026

Received on Tuesday, 18 August 2020 23:20:46 UTC