- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jan 2020 16:01:06 +0000
- To: public-css-archive@w3.org
I'm less than enthusiastic about the suggestion on the Dec 11 call to roll back the [consistent hyphenaton](https://github.com/w3c/csswg-drafts/issues/4056#issuecomment-546539874) for built-in color profiles. I agree with @AmeliaBR and @fantasai that is we make them exactly the same as the built-in colorspaces, then people will assume they are testing for *that exact profile* and will then also want a bunch of other profiles added. This is very different to the 'roughly sRGB' | `common wide gamut` | `superwide 4k TV gamut` buckets for MQ. As I said earlier, if this was being designed now then maybe better keywords could be used but then there would be a drawback on that. Given that it shipped already in 2 browsers the cost of bikeshedding (there is always a cost, but this time it is high) seems excessive. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4535#issuecomment-574726935 using your GitHub account
Received on Wednesday, 15 January 2020 16:01:08 UTC