I'm excited by this one! Think I'll add dark mode support to my simple blog right now.
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=889087
Why layer something like this on top of an override system, when devs can choose to just not override those things?
As an example, the only CSS colours I use on chriswarbo.net are either semi-transparent, or mid-grey (which work on light and dark themes, although I might revisit that since it would presumably not work on default-grey systems like AmigaOS).
Not yet, although the API seems open enough to add this.
For accessibility reasons, using the zoom feature is much more stable than increasing the default font size.
Which users choose according to their preferences (e.g. Firefox offers a preferences dialogue for this, and a bunch of about:config options). Whilst most users leave these as the OS/browser vendor's defaults, (in the words of Rush) "if you choose not to decide, you still have made a choice".
> When font changes are inherited from user's settings however, it basically just breaks everything.
> For accessibility reasons, using the zoom feature is much more stable than increasing the default font size.
So you're agreeing that all these sites are broken?
Of course, the majority of websites apply their own font styling so this doesn't often come up anymore. But those settings are just death traps at this point. Ineffective in 90% of cases, and hazardous in the 10% where they do work.
Now to wait for better browser support.