← back to v133 · popover-nested-inside-invoker-shouldn-t-re-invoke-it
conformance · v133
v133 · popover-nested-inside-invoker-shouldn-t-re-invoke-it — 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 |
|---|---|---|---|---|
popover-api-exposed |
HTMLElement.popover is exposed; the fix is behavioural, not a new API surface. | script | … | |
showpopover-exposed |
showPopover is callable. | script | … | |
toggle-event-exposed |
ToggleEvent is exposed; popovers fire it on open/close. | exists | … | |
double-show-throws-invalidstate |
Calling showPopover on an already-open popover throws InvalidStateError (the fix relies on this rather than re-firing toggle). spec ↗ | script | … | |
popovertargetaction-toggle-still-supported |
popovertargetaction='toggle' remains accepted on invokers. | script | … |