- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jun 2020 17:19:52 +0000
- To: public-css-archive@w3.org
Accent color isn't indicating what's being colored, either. I'd say if there isn't a compat restriction, re-using `color` here makes a fair amount of sense unless there's a need to indicate two different colors as input. FWIW, the CSS UI spec [used to say](https://www.w3.org/TR/2004/CR-css3-ui-20040511/#appearance1) > If 'appearance' is not 'normal', the UA must render the element as if it was the specified user interface (UI) control from the platform. The UA should use the computed values of the 'background-*', 'border-*', 'padding-*', 'outline-*', and 'text-decoration' properties when they do not have their initial values and the computed values of 'color', 'font', and 'cursor' (whatever their values) to influence the rendering where possible. Any values from those properties that cannot be used to influence the rendering of the UI control must not affect the rendering at all. For example, the UA should not draw a second border around a UI control that already has a border. If 'background-color' or 'background-image' have non-initial values and the UA is using their values for influencing the rendering of the UI control, then the UA must ensure that the 'color' property is also used to influence the rendering. That seems to have gotten lost along the way... //CC @tantek -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-641458651 using your GitHub account
Received on Tuesday, 9 June 2020 17:19:54 UTC