← back to v146 · scoped-custom-element-registry
conformance · v146
v146 · scoped-custom-element-registry — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
customelementregistry-constructible |
CustomElementRegistry now has a public constructor — `new CustomElementRegistry()` succeeds. | script | … | |
scoped-registry-define-method |
An instance of CustomElementRegistry exposes define() with the standard signature. | script | … | |
attachshadow-accepts-customelements-option |
Element.attachShadow accepts a customElements option pointing at a scoped registry. | script | … | |
shadowroot-exposes-customelements-getter |
ShadowRoot exposes a customElements getter so script can introspect which registry is in effect. | script | … | |
createelement-takes-registry-option |
Document.createElement accepts a customElementRegistry option so factory functions can use scoped registrations. | script | … | |
global-customelements-still-present |
The legacy global window.customElements registry remains for backwards compatibility. | script | … |