Re: [w3ctag/design-reviews] EyeDropper API (#587)

Does the TAG have concrete suggestions for how the input element could be extended to support device independent colors in a backwards compatible way? Maybe that could be used as model here.

E.g. the `<input type=color>`'s  `value` property would need to continue to be sRGB hex to avoid breaking sites, but maybe there could be a `color` property added which is only not undefined for color inputs, and is a CSSOM type (?) that provides forward-compatibility to access/translate colors between color spaces in a defined way. I don't think such a thing exists yet, though.

In that case, this API could follow that model - `value` on the event continues to be an sRGB hex, but once the device-independent, forward-compatible color type is added to the platform it could be added to the event as `color`.

This is a half-baked idea; I'm hoping the TAG can suggest something more practicable.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/587#issuecomment-762953190