← back to v136 · remove-htmlfencedframeelement-canloadopaqueurl
conformance · v136
v136 · remove-htmlfencedframeelement-canloadopaqueurl — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
can-load-opaque-url-removed |
HTMLFencedFrameElement.canLoadOpaqueURL is no longer defined — the deprecated static accessor has been removed. spec ↗ | script | … | |
can-load-ad-auction-fenced-frame-replacement |
The replacement API navigator.canLoadAdAuctionFencedFrame is defined (function) — verifies the migration target is the one Chrome supports. | script | … | |
fenced-frame-element-may-be-absent |
If the element is exposed, it must still be a function (constructor) — it was not removed, only the static helper was. | script | … | |
fenced-frame-config-may-be-exposed |
FencedFrameConfig — the modern way to load opaque content into a fenced frame — is either undefined (no fenced frames) or a constructor. | script | … | |
call-removed-method-throws |
Calling the removed canLoadOpaqueURL() static throws (it is not callable). | script | … |