This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The interfaces in the explainer don't match what's in the Shadow DOM spec (possibly for those defined in the templates spec too--I haven't gotten through that one yet). I suspect they just fell out of sync. Some examples: - no mention of PseudoElementStylable interface and pseudo attribute - "ShadowRoot implements NodeSelector;" no mention of this in Shadow DOM spec. - HTMLContentElement interface missing resetStyleInheritance, getDistributedNodes() - HTMLShadowElement interface missing resetStyleInheritance - ShadowRoot interface: - Element vs. HTMLElement type for getElementById - "in DOMString" vs. "DOMString" - nullable DOMString? vs. "DOMString" - missing getSelection - missing addStyleSheet, removeStyleSheet - no selection attribute in Shadow DOM spec - missing StyleSheetList In Appendix B, the <content> element is missing the reset-style-inheritance attribute.
Just had a read of the HTML Templates spec. Templates spec: interface HTMLTemplateElement : HTMLElement { attribute DocumentFragment content; } Explainer: interface HTMLTemplateElement : HTMLElement { readonly attribute DocumentFragment content; } And in Appendix B of the explainer, the content attribute is missing
Instead of duplicating the definitions I have reduced the appendix to linking directly to the normative definitions. Do you think attributes and operations are also interesting to include in the index? Or are elements and interfaces sufficient? <https://dvcs.w3.org/hg/webcomponents/rev/9f893b16938a>