Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

innerHTML should be defined on ShadowRoot interface in addition to Element interface #21

Closed
rniwa opened this issue Sep 29, 2016 · 6 comments

Comments

@rniwa
Copy link

rniwa commented Sep 29, 2016

In the world where ShadowRoot interface is merged into DOM (as done in the WHATWG version), it's more natural for the DOM parsing & serialization spec to define innerHTML IDL attribute on both Element and ShadowRoot interfaces.

@foolip
Copy link
Member

foolip commented Mar 9, 2017

FWIW, Chromium and WebKit both have this already. (I came here trying to figure out what to do about that.)

@domenic
Copy link
Collaborator

domenic commented Oct 22, 2018

The hard part here is figuring out the context element. Once we do that, it's easy to spec. @rniwa @tkent-google @smaug---- can you let us know what your implementations of ShadowRoot's innerHTML do in that regard?

@rniwa
Copy link
Author

rniwa commented Oct 22, 2018

WebKit uses the host element as the context element.

@smaug----
Copy link

@tkent-google
Copy link

Blink also uses the host element.

@rniwa
Copy link
Author

rniwa commented Nov 6, 2018

Sounds like this is ready to be spec'ed as such then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants