← back to v146 · preserving-dropeffect-values-from-dragover-to-drop-events
conformance · v146
v146 · preserving-dropeffect-values-from-dragover-to-drop-events — 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 |
|---|---|---|---|---|
datatransfer-interface-exposed |
The DataTransfer interface is exposed — the carrier object whose dropEffect now persists from dragover to drop. | exists | … | |
datatransfer-has-dropeffect |
DataTransfer exposes the dropEffect accessor. | script | … | |
datatransfer-dropeffect-defaults-to-none |
A freshly constructed DataTransfer reports dropEffect 'none' by default. | script | … | |
datatransfer-dropeffect-accepts-known-values |
dropEffect accepts the known values 'copy', 'move', 'link', and 'none' as per spec. | script | … | |
datatransfer-dropeffect-rejects-invalid-string |
Assigning an unrecognised value to dropEffect leaves the previous value intact (per spec the setter ignores invalid input). | script | … | |
drag-event-types-still-fire |
The 'dragover' and 'drop' event names remain the standard surface; both register without throwing. | script | … |