Answer prose round 1: 0 🔴, 7 🟡 (0 misread); the header opens with what it checks, README says what fails even guarded and how a plugin is checked, the changelog stops claiming a floor change
CI / full-gate (push) Successful in 3m23s
Mirror / github-mirror (push) Successful in 4s

This commit was merged in pull request #197.
This commit is contained in:
2026-10-31 12:13:32 +01:00
parent 7539f8ec0d
commit 8a93d59988
2 changed files with 10 additions and 9 deletions
+4 -4
View File
@@ -8,10 +8,10 @@ at boot. Entries start at 0.3.0.
### The tests fail on a stylesheet feature the browser floor lacks
Every stylesheet in the repo, the examples' included, is checked against Chromium 87, Safari 15 and
Firefox 115 using MDN's compat data; a feature one of them lacks passes only inside an `@supports`
that names it. The core stylesheets now guard each such feature, which those engines skip instead
of misreading. Pages render as before in current browsers.
`npm test` checks every stylesheet in `public/`, `examples/` and `plugins/` against Chromium 87,
Safari 15 and Firefox 115: a feature one of them lacks fails it unless an `@supports` around it
names that feature. Mount a plugin in `plugins/<id>/` to check its stylesheets. Pages render as
before in every browser.
### Every release reaches Docker Hub, and the Hub page has a short description