- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 00:40:57 +0000
- To: public-css-archive@w3.org
@Crissov The actual use cases need access to the actual generic font families like `sans-serif` or `monospace`. But yes, the efforts to redefine existing keywords to express page-specific styles would benefit from more coordination. I was even thinking that keywords like `smaller`/`larger` or `thin`/`medium`/`thick` could benefit from the ability to be redefined. There is no reason to have existing keywords that resolve to OS or UA design tokens when they could resolve to page-specific tokens that would be infinitely more useful. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10452#issuecomment-2378187435 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 September 2024 00:40:57 UTC