From 8a93d59988dd425ddc6fb0bbe87f1872b307c24d Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Sat, 31 Oct 2026 12:13:32 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20prose=20round=201:=200=20=F0=9F=94=B4,?= =?UTF-8?q?=207=20=F0=9F=9F=A1=20(0=20misread);=20the=20header=20opens=20w?= =?UTF-8?q?ith=20what=20it=20checks,=20README=20says=20what=20fails=20even?= =?UTF-8?q?=20guarded=20and=20how=20a=20plugin=20is=20checked,=20the=20cha?= =?UTF-8?q?ngelog=20stops=20claiming=20a=20floor=20change?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 8 ++++---- README.md | 11 ++++++----- 2 files changed, 10 insertions(+), 9 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f1b3512..c005e02 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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//` to check its stylesheets. Pages render as +before in every browser. ### Every release reaches Docker Hub, and the Hub page has a short description diff --git a/README.md b/README.md index 2c1b130..8e6b706 100644 --- a/README.md +++ b/README.md @@ -1059,11 +1059,12 @@ Chromium 87, Safari 15 and Firefox 115, the engines in years-old TVs, kiosks and features [Baseline Widely available](https://web-platform-dx.github.io/baseline/) (in every major engine for 30 months) may shape how a page looks; anything newer, like popovers or anchor positioning, only enhances. A feature the floor engines lack, such as `:has()`, may -decorate a page but never decide whether something shows or can be read. The tests hold every -stylesheet in `public/` and `examples/` to this floor, against MDN's compat data: a feature a floor -engine lacks fails them unless it sits inside an `@supports` whose condition names it -(`src/ui/stylesheet-floor.ts` lists what it checks). A plugin stylesheet mounted from outside the -repo is not checked. +decorate a page but never decide whether something shows or can be read. `npm test` fails on a +stylesheet using a feature Chromium 87, Safari 15 or Firefox 115 lacks, unless an `@supports` +around it names that feature. It checks every stylesheet in `public/`, `examples/` and `plugins/`, +so mount your plugin in `plugins//` and run it. A few constructs fail even when guarded, such as +`@layer`, nested rules and media range syntax, while a media feature passes unguarded, since a +browser without it skips the query; `src/ui/stylesheet-floor.ts` lists the rules. **A field whose options depend on another field is asked for in steps, one GET form each**, so every choice is in the URL, and nothing typed is lost to one because nothing is typed until they are made.