← back to v143 · menu-elements

conformance · v143

v143 · menu-elements — conformance probe

7 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.

browser: spec: https://github.com/whatwg/html/pull/12011 chromestatus: #5206029088063488 generated 2026-08-28T00:00:00Z by claude-opus-5-v143-build
0
pass
0
fail
0
blocked
7
total
id contract kind verdict detail
menuitem-has-its-own-interface The element exists as an element rather than as an unknown tag. HTMLUnknownElement is what every browser produces for a tag it has never heard of, so this is the difference between an implementation and a parse. spec ↗ script
menulist-and-menubar-have-their-own-interfaces Both containers are real elements too, even though neither carries any IDL of its own — their behaviour is layout, top-layer participation and accessibility mapping. spec ↗ script
menulist-is-hidden-until-invoked A menulist sits inline in the markup beside the title that opens it, so the user-agent stylesheet must hide it. Anything other than display:none would mean every menu on the page is visible at load. spec ↗ script
menuitem-reflects-command-and-commandfor A menu item invokes through the invoker command attributes rather than a click handler, and commandfor reflects as an element reference — which only resolves inside a document. spec ↗ script
unknown-commands-reflect-as-the-empty-string command is an enumerated attribute, so a keyword it does not know reads back as the empty string. That is what makes the reflection a per-keyword support probe rather than an all-or-nothing one. spec ↗ script
custom-commands-need-two-dashes A name beginning with two dashes is passed through verbatim; the same name without them is reserved for the platform and is discarded. Without that rule an application's command could collide with a future built-in. spec ↗ script
invoking-a-menuitem-opens-its-menulist The whole markup-only claim in one check: a menuitem carrying command=toggle-menu opens the menulist it points at, and the opened menulist is in the top layer — matched by :popover-open, with no popover attribute anywhere. spec ↗ script