- From: Coises <Randy@Coises.com>
- Date: Sun, 25 Aug 2002 13:56:51 -0700
- To: www-style@w3.org
[Thu, 22 Aug 2002 22:19:34 -0400] fantasai:
>I think we need an 'auto' value for the content property.
It seems this is anticipated here:
http://www.w3.org/TR/2002/WD-css3-lists-20020220/#list-content0
where it is assumed that "none" and "auto" will be defined for the
"content" property. (As yet, no working draft for the Generated Content
module of CSS3 has been published, so we can't look up "content" directly.)
In his follow-up to your message, archived at:
http://lists.w3.org/Archives/Public/www-style/2001Jun/0008.html
Ian Hickson writes:
|| The initial value of 'content' should not be the empty string,
|| it should be nothing at all. This is similar to border-color, whose
|| initial value is not representable in CSS (yet). This is a known error
|| that will be corrected in CSS3.
which notes the same problem.
CSS3 in effect corrects these problems because it adds the keyword
"initial" as an allowed value for all properties:
http://www.w3.org/TR/2002/WD-css3-cascade-20020219/#initial
(as well as implying that "none" and "auto" will be defined for "content").
If these are indeed recognized as "known errors" in CSS2, then it would
seem they should be corrected in CSS 2.1. I would suggest introducing:
content: none
as the appropriate CSS 2.1 value (since "content: auto" could only mean
"none" in CSS 2.1). It also seems to me that CSS 2.1 and CSS 3 would be
best changed to include "auto" as a border color value. (However, if it is
not desired to introduce "auto" as a border color value in CSS 3, then we
should instead allow "initial" as a border color value in CSS 2.1.)
--
Randall Joseph Fellmy aka Randy@Coises.com
Received on Sunday, 25 August 2002 16:57:23 UTC