- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Sun, 06 Aug 2023 13:55:23 +0000
- To: public-css-archive@w3.org
> Is it a goal of the WICG Color API to ever provide similar gamut-mapping function to the user? If so, should all instances of gamut mapping, (or at least the directly/indirectly accessible functions) work against a list of predefined, approximate gamuts, a la [`color-gamut`](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/color-gamut) media query? I think that preventing any API that has some slight risk of fingerprinting is an anti pattern and instead the potential drawbacks should be weighed against the potential benefits. We see this in HDR where knowledge of the ambient light level is needed to calculate the HDR headroom but there is a fingerprint worry so ok we can't expose that and in consequence **the user can't see the HDR image or video at all** because the sun is shining but hey at least we preserved 0.1 bits of fingerprint entropy. Getting back to the specific question - yes I think Color API should provide that function, which will be way more consistent, simpler and likely more efficient than forcing users to implement it themselves. But such things should be raised and discussed [on the Color API repo](https://github.com/WICG/color-api/issues) -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8539#issuecomment-1666868631 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 6 August 2023 13:55:25 UTC