← back to v145 · remove-bmp-extension-for-embedding-jpeg-or-png-in-bmp
conformance · v145
v145 · remove-bmp-extension-for-embedding-jpeg-or-png-in-bmp — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
image-element-still-exists |
HTMLImageElement remains exposed — only the BMP-with-embedded-PNG/JPEG extension is removed; image/bmp itself still decodes. | exists | … | |
image-decode-is-function |
HTMLImageElement.prototype.decode is a function — the promise-based decode that should now reject for embedded-PNG/JPEG-in-BMP. | typeof | … | |
plain-bmp-still-decodes |
A minimal plain image/bmp data URL still decodes successfully — the removal is scoped to the embedding extension. | script | … | |
bmp-embedded-png-rejects |
Attempting to decode an image/bmp whose payload is a PNG signature settles through the image decoder rather than throwing synchronously. spec ↗ | script | … | |
fetch-image-still-available |
fetch is exposed — the alternative decode path also no longer accepts the BMP embedding extension. | typeof | … |