MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry
What information is incomplete?
The HTML Standard is adding the scopedcustomelementregistry global content attribute and the reflecting HTMLElement.scopedCustomElementRegistry IDL attribute.
The content attribute affects HTML parser creation: the element and its parsed subtree begin with a null custom element registry so a scoped CustomElementRegistry can claim the subtree later through initialize(). Changing the attribute after element creation does not change the assigned registry. The IDL attribute reflects as a DOMString for future extensibility.
What should be documented?
- The
scopedcustomelementregistry global attribute.
HTMLElement.scopedCustomElementRegistry string reflection.
- Parser-only behavior and the relationship to
CustomElementRegistry.initialize().
- Serialization behavior at custom element registry boundaries.
- Browser compatibility once implementations adopt the final specification.
References
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry
What information is incomplete?
The HTML Standard is adding the
scopedcustomelementregistryglobal content attribute and the reflectingHTMLElement.scopedCustomElementRegistryIDL attribute.The content attribute affects HTML parser creation: the element and its parsed subtree begin with a null custom element registry so a scoped
CustomElementRegistrycan claim the subtree later throughinitialize(). Changing the attribute after element creation does not change the assigned registry. The IDL attribute reflects as aDOMStringfor future extensibility.What should be documented?
scopedcustomelementregistryglobal attribute.HTMLElement.scopedCustomElementRegistrystring reflection.CustomElementRegistry.initialize().References