- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 27 Mar 2014 12:52:43 -0700
- To: Simon Sapin <simon.sapin@exyr.org>
- Cc: www-style list <www-style@w3.org>
On Thu, Mar 27, 2014 at 12:03 PM, Simon Sapin <simon.sapin@exyr.org> wrote: > On 27/03/2014 18:19, Tab Atkins Jr. wrote: >> >> On Wed, Mar 26, 2014 at 3:21 PM, Simon Sapin <simon.sapin@exyr.org> wrote: >>> >>> >>> https://dvcs.w3.org/hg/csswg/raw-file/931f8a9374a1/css-color/Overview.html#cmyk-colors >>> says: >>>> >>>> If the user agent has information about the output device such that >>>> it believes it can accurately convert the CMYK color to a correct RGB >>>> color, the computed value of the device-cmyk() function must be that >>>> RGBA color. Otherwise, the computed value must be the fallback color. >>> >>> >>> Can this be a used value rather a computed value? >>> >>> Unless we really intend to have the effects on the inherited value and >>> getComputedStyle(), doing this kind of tweaks at computed-value-time adds >>> implementation complexity needlessly. (Which as usual leads to risk of >>> some >>> implementations accidentally getting this wrong, hurting interop, etc.) >> >> >> Why does this need to wait until used-value time? There's nothing >> about this that depends on layout-information - it should be purely >> *ambient* information. > > > It doesn’t need to, but I think making it computed-value-time adds > complexity to implementations needlessly. > > Also, do we want this to affect the inherited value? It's a global effect, isn't it? ~TJ
Received on Thursday, 27 March 2014 19:53:33 UTC