← back to v158 · spec-compliant-xml-mime-type-detection
conformance · v158
v158 · spec-compliant-xml-mime-type-detection — 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 |
|---|---|---|---|---|
resource-timing-exists |
PerformanceResourceTiming exists (the surface whose classification this feature changes). spec ↗ | typeof | … | |
contenttype-attribute-exists |
PerformanceResourceTiming.prototype exposes contentType, the minimized-MIME-type observable (Chrome 148+). spec ↗ | script | … | |
text-plus-xml-minimizes-to-application-xml |
A real same-origin response served as text/example+xml minimizes to application/xml — the core of the spec rule: any valid MIME type whose subtype ends in +xml is an XML MIME type. spec ↗ | script | … | |
image-plus-xml-minimizes-to-application-xml |
A response served as image/example+xml also minimizes to application/xml — the rule covers every valid top-level type, not just application/*. spec ↗ | script | … | |
application-plus-xml-minimizes-to-application-xml |
application/example+xml minimizes to application/xml — the half of the suffix rule Chrome applied all along; a regression here would be worse than the old behaviour. spec ↗ | script | … | |
svg-keeps-its-own-essence |
image/svg+xml does NOT minimize to application/xml: minimize-a-supported-MIME-type returns the essence for SVG, the deliberate exception to the +xml rule. spec ↗ | script | … | |
non-xml-control-not-swept-in |
text/plain does not become application/xml — guards against an over-broad implementation that would sweep non-+xml types into the XML bucket. spec ↗ | script | … |