← back to v152 · gamepad-button-type-attribute
conformance · v152
v152 · gamepad-button-type-attribute — 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 |
|---|---|---|---|---|
gamepad-api-available |
The API this property is added to. spec ↗ | typeof | … | |
gamepadbutton-interface-exists |
The interface carrying the new property. Its members can be read without a controller connected, which is what makes this feature probeable on any machine. spec ↗ | typeof | … | |
gamepadbutton-has-pressed-touched-and-value |
The three properties that exist today. They describe a button's state completely and say nothing about its identity, which is the gap this feature fills. spec ↗ | script | … | |
gamepadbutton-has-type |
The feature: a button names itself, so a control past the seventeen standard positions can be identified without matching on the device id string. spec ↗ | script | … | |
gamepad-exposes-id-and-mapping |
The two members an application currently reasons about: a free-text id, and whether the standard mapping applies. Both must exist for the workaround this feature replaces to be describable at all. spec ↗ | script | … | |
getgamepads-returns-a-list-without-a-controller |
Calling it with nothing connected must return a list rather than throwing, so a page can probe the API on any machine. A browser also withholds gamepads until the user has interacted with one, which is why every demo here degrades rather than waiting. spec ↗ | script | … |