- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Mar 2024 00:21:56 +0000
- To: public-css-archive@w3.org
To quote from [info.cern.ch](https://info.cern.ch/hypertext/WWW/MarkUp/HTMLConstraints.html#:~:text=It%20is%20required%20that%20HTML%20be%20a%20common%20language%20between%20all%20platforms.%20This%20implies%20no%20device%2Dspecific%20markup%2C%20or%20anything%20which%20requires%20control%20over%20fonts%20or%20colors%2C%20for%20example.) (emphasis added) > It is required that HTML be a common language between all platforms. This implies no device-specific markup, **or anything which requires control over fonts or colors, for example.** We have strayed so far from the light… Anyway, I think it's helpful to talk about the range use-cases here, from color matching to generated palettes to gradients. But it seems to me essential we come back to a baseline understanding of CSS as a resilient cross-device language for providing presentational hints and suggestions, to be ignored when necessary in favor of usability. That's a different set of priorities from most design tools and image/video formats. And it doesn't alway lead us to the _prettiest_ default in every situation (see text overflow 'honking right out of the box') but hopefully it leaves us with a more resilient platform, and a web that's world-wide. _When an author defines colors that are outside the display gamut - however the author got there - browsers need a way to recover. How do we ensure that recovery is as resilient as possible across a web for everyone, on everything?_ -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2010957450 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 March 2024 00:21:57 UTC