← back to v132 · pushmessagedata-bytes
conformance · v132
v132 · pushmessagedata-bytes — 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.
0
pass
0
fail
0
blocked
7
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
pushmessagedata-interface-exposed |
PushMessageData is exposed in window scope. spec ↗ | script | … | |
pushmessagedata-bytes-method |
PushMessageData.prototype.bytes exists. spec ↗ | script | … | |
pushmessagedata-bytes-is-function |
PushMessageData.prototype.bytes is a function. | script | … | |
pushmessagedata-arraybuffer-still-exists |
The legacy arrayBuffer() accessor remains alongside bytes(). | script | … | |
pushmessagedata-text-still-exists |
The legacy text() accessor remains alongside bytes(). | script | … | |
pushmessagedata-blob-still-exists |
The legacy blob() accessor remains alongside bytes(). | script | … | |
pushmessagedata-json-still-exists |
The legacy json() accessor remains alongside bytes(). | script | … |