Gregory's Server@pepelsbey yes! Exactly that. There's a half finished prototype in chromium behind the experimental flag if you wanted to try it out.
|
5 comments
 @argyleink @Lukew @pepelsbey @bramus Quick question, I did not find an answer in the spec: is there a way to access the original, non-overridden, user preference? A hacky way would be to clear the override, read the value, restore the override, but that feels too bad. There are legit cases when you'd want to override the value that is used everywhere, but then still be able to differentiate how things look/behave based both on the original value, and on the override. @argyleink @Lukew @pepelsbey @bramus (for the last point — see https://blog.kizu.dev/querying-the-color-scheme/#not-the-user-preference, for example — it is the same issue basically) @kizu @argyleink @pepelsbey @bramus ooh that's an interesting point! There currently isn't a way to do that. https://github.com/wicg/web-preferences-api/issues/ if you can it'd great if you left an issue here and then I'll get them all migrated over to the CSS repo when back at a computer. No worries if you can't I'll hopefully remember to. |
@Lukew @pepelsbey i was just trying it yesterday with @bramus 's extension 🤘🏻