- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Sun, 16 Jun 2024 11:09:32 +0000
- To: public-css-archive@w3.org
@Crissov > I once proposed to enable authors to redefine color keywords – and was told this was a bad idea. It’s not uncommon for proposals to get rejected for years before they get accepted, for a variety of reasons. E.g. inline `if()` was [rejected in 2018](https://github.com/w3c/csswg-drafts/issues/3455) and [accepted recently](https://github.com/w3c/csswg-drafts/issues/10064). Or your proposal for redefining system colors vs redefining system colors getting accepted in #9660 😄 > Although most originate in the Unix/Linux/X11 world, the (non-System) color keywords have universal definitions across browsers, both in theory and practice, whereas generic font family keywords, at least in theory, depend on OS and browser settings or defaults – in practice, it’s not always possible for users to choose different typefaces, or they can just do so indirectly via themes. Web pages are already able to define their own fonts, and do so to great extent so that ship has sailed (more than two decades ago lol). This is about included UI components being able to read which fonts the page is using. > Furthermore, is this proposal only about classic generic font keywords or also about those inside `generic()`? I think starting from generic font keywords is a good MVP, we can always extend it if the need arises. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10452#issuecomment-2171440418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 16 June 2024 11:09:33 UTC