← back to v152 · deprecate-and-remove-xslt
conformance · v152
v152 · deprecate-and-remove-xslt — 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 |
|---|---|---|---|---|
xsltprocessor-exists-or-not |
XSLTProcessor is still exposed during the deprecation window — once removal completes, this will be undefined. spec ↗ | exists | … | |
xsltprocessor-is-function |
If XSLTProcessor remains, it is a constructor (function). spec ↗ | script | … | |
xsltprocessor-importstylesheet-present |
If XSLTProcessor exists it must expose importStylesheet on its prototype. spec ↗ | script | … | |
xsltprocessor-transform-present |
If XSLTProcessor exists it must expose transformToFragment on its prototype. spec ↗ | script | … | |
xml-stylesheet-pi-still-parses |
An xml-stylesheet PI in an XML document still parses (DOMParser does not throw); whether XSLT is applied is a separate UA decision. spec ↗ | script | … | |
deprecation-reporting-deprecation-source |
ReportingObserver / DeprecationReport is exposed so the deprecation can be observed. spec ↗ | exists | … |