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

[css3 Generated content] Why is content:normal not implied?

From: dolphinling <lists@dolphinling.net>
Date: Thu, 01 Dec 2005 19:38:14 -0500
Message-ID: <438F9776.3090902@dolphinling.net>
To: W3C CSS List <www-style@w3.org>

http://www.w3.org/TR/2003/WD-css3-content-20030514/#content

| If no alternatives exist, then 'none' is used as a final fallback, so
| in the example above, if 'header/png' wasn't available either, then
| the <h1> element would be empty.
|
| Thus to make an element fallback on its contents, you have to
| explicitly give 'contents' as a fallback:
|
| content: url(1), url(2), url(3), contents;

I think it would be better to say that if 'contents' is not found in the 
list of values, it is implied to be at the end.

As it stands, I think lots of authors will simply write

h1 { content: url(1); }

without testing, and if the image goes unavailable there will be no 
fallback.
-- 
dolphinling
<http://dolphinling.net/>
Received on Friday, 2 December 2005 00:38:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:42 GMT