- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 04:50:05 +0000
- To: public-css-archive@w3.org
I'd note that, when the system theme is dark, we get a bunch of complaints from users (see, e.g., the recent activity in [bug 70315](https://bugzilla.mozilla.org/show_bug.cgi?id=70315)) complaining that Web pages are broken when dark defaults are applied. Given this, I think I'd be happy with **a mode that indicates that a page is capable of rendering correctly with *either* light or dark themes**. This would allow UAs capable of doing so to, if they wish, when the system theme is dark and a page does *not* have this indicator, render the "system" controls as colors as a light theme instead of the dark one. Given that, today, pages all work with light themes, it seems like it would be a step backward to allow pages to do the opposite, and force dark controls/colors when the user has a light system theme. I think that's a bad idea for two reasons: 1. it means that user preferences that work today will stop working 2. it creates additional problems that don't exist today for UAs that are unable to implement this reasonably. UAs might have problems implementing this if the system's theming mechanism doesn't have a clear way to switch between "equivalent" light and dark themes. I think this is true of GTK (based on familiarity with the theme switching UI and with the underlying APIs), and I think also older versions of Windows (though not Windows 10, I think), based on experience with the Windows 10 UI, and with the UI and API on substantially older versions. (I'm not sure where the change was, though!) (I'd note that GTK used to have a way for an app to force a dark system theme to be light, but not the reverse, and that mechanism was recently removed.) -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3299#issuecomment-463057095 using your GitHub account
Received on Wednesday, 13 February 2019 04:50:08 UTC