From 270d80c8d048bf1c4f159aa67002a1337e74ccd5 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Sat, 31 Oct 2026 01:07:30 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20prose=20round=201:=200=20=F0=9F=94=B4,?= =?UTF-8?q?=203=20=F0=9F=9F=A1=20(0=20misread);=20state=20the=20colour=20r?= =?UTF-8?q?ule=20in=20the=20README=20and=20the=20changelog?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 5 +++-- README.md | 6 ++++-- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 95b99d5..2fd8fd4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,8 +9,9 @@ at boot. Entries start at 0.3.0. ### Colours render on engines without `oklch()` The theme palette in `public/css/styles.css` is hex, not `oklch()`. On an engine older than -Chromium 111 (Tizen 2024, webOS TV 24) the accent token was invalid, so the primary button was white -text on no background. A plugin that overrides a palette token should use a hex value too. +Chromium 111 (Tizen 2024, webOS TV 24) `var(--accent)` was invalid, so the primary button was white +text on no background. A plugin that sets a colour custom property, such as `--accent` or `--l-accent`, +should use hex, `rgb()` or `hsl()` too. ### One horizontal inset across the content pane diff --git a/README.md b/README.md index 9bcdd2c..b5deb5c 100644 --- a/README.md +++ b/README.md @@ -1023,8 +1023,10 @@ URL is the only state the UI keeps. Chromium 87, Safari 15 and Firefox 115, the engines in years-old TVs, kiosks and Qt panels. Only 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()` or `oklch()`, may -decorate a page but never decide whether something shows or can be read. +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. A colour is hex, `rgb()` or +`hsl()`, never `oklch()`: a custom property holding it passes unchecked, and the `var()` reading it +then renders transparent. **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.