← back to v155 · remove-fencedframe-element-and-window-fence-apis
conformance · v155
v155 · remove-fencedframe-element-and-window-fence-apis — conformance probe
4 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
4
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
createelement-never-returns-null |
createElement returns an element for any name that is a valid element name, whether or not the browser has ever heard of it. A truthiness check on the result therefore cannot detect this removal, or any other — which is the mistake this feature's migration page exists to head off. spec ↗ | script | … | |
an-unregistered-tag-becomes-htmlunknownelement |
The end state of the removal, demonstrated on a tag no browser has ever implemented: an element name that is not registered produces an HTMLUnknownElement, which has none of the removed element's properties. This is what fencedframe becomes. spec ↗ | script | … | |
the-element-and-its-config-property-agree |
The interface object and the config property are removed together, so a page may test for either and get the same answer. Holds on both sides of the removal: both true while the element exists, both false once it does not. spec ↗ | script | … | |
a-config-cannot-be-constructed-from-script |
FencedFrameConfig has no constructor exposed to pages: a config may only be produced by an auction or by Shared Storage. This is why removing those producers is sufficient to make the element unusable, and it holds vacuously once the interface itself is gone. spec ↗ | script | … |