W3C home > Mailing lists > Public > www-style@w3.org > December 2012

[css3-color] Issues with edits for currentColor being a computed value

From: L. David Baron <dbaron@dbaron.org>
Date: Wed, 19 Dec 2012 13:44:01 -0500
To: www-style@w3.org
Message-ID: <20121219184401.GA13577@crum.dbaron.org>
The working group agreed to revise css3-color so that currentColor
is a computed value.  The edit made in the editor's draft is exactly
what is described in the REC's errata:

However, I think this edit is incorrect.

In particular, 'currentColor' **for the 'color' property** must
still be resolved at computed value time.  'color: currentColor'
should be treated just like 'color: inherit', including resolving
the value to an actual color at computed value time.  I'm not even
sure what it would mean to do otherwise.

Thus I propose the following additional errata on top of the current

 (1) In “4.4. ‘currentColor’ color keyword”, change:

     If the ‘currentColor’ keyword is set on the ‘color’ property
     itself, it is treated as ‘color: inherit’ <ins>when determining
     the computed value for ‘color’</ins>.

 (2) In “3.1. Foreground color: the ‘color’ property”, add, in the
     place of the previous removal (in the errata):

     <ins>The computed value for 'currentColor' or for 'inherit' is
     the computed value from the parent element, or, for the root
     element, which has no parent element, the initial value.</ins>

(In the errata list, these could both be merged into the existing
errata item.)


𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                           http://www.mozilla.org/   𝄂
Received on Wednesday, 19 December 2012 18:44:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:24 UTC