-
Notifications
You must be signed in to change notification settings - Fork 14
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
Comments
FWIW, Chromium and WebKit both have this already. (I came here trying to figure out what to do about that.) |
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? |
WebKit uses the host element as the context element. |
(Github is behaving oddly today) Gecko uses host as context, https://searchfox.org/mozilla-central/rev/0ec9f5972ef3e4a479720630ad7285a03776cdfc/dom/base/FragmentOrElement.cpp#2309-2313 |
Blink also uses the host element. |
Sounds like this is ready to be spec'ed as such then. |
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 defineinnerHTML
IDL attribute on bothElement
andShadowRoot
interfaces.The text was updated successfully, but these errors were encountered: