← back to v145 · inputevent-types-for-deletion-commands-on-non-collapsed-selections
conformance · v145
v145 · inputevent-types-for-deletion-commands-on-non-collapsed-selections — 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 |
|---|---|---|---|---|
input-event-interface-exists |
InputEvent is exposed — the event type whose inputType reports the deletion command. | exists | … | |
input-event-input-type-attribute |
InputEvent.prototype exposes inputType — the attribute that now reports deleteContentBackward/Forward over deleteWordBackward/Forward when selection is non-collapsed. spec ↗ | script | … | |
input-event-target-ranges-exists |
InputEvent.prototype.getTargetRanges is a function — exposes the range that will be deleted. spec ↗ | script | … | |
content-editable-attribute-supported |
contentEditable is supported on HTMLElement — the surface where deletion inputType is observed. | script | … | |
input-event-constructible-with-input-type |
InputEvent can be constructed with an inputType — used by tests and synthetic input. spec ↗ | script | … | |
selection-api-exists |
getSelection() is exposed — the API used to read the non-collapsed selection state these inputTypes now report on. | typeof | … |