- From: Dão Gottwald <dao@design-noir.de>
- Date: Fri, 18 May 2007 19:08:43 +0200
- To: Elliott Sprehn <esprehn@gmail.com>
- CC: Dmitry Turin <html60@narod.ru>, public-html@w3.org
Elliott Sprehn schrieb:
>
> On May 18, 2007, at 8:58 AM, Dmitry Turin wrote:
>
>>
>> Good day, Dao.
>> Excuse me for a long break.
>>
>> DG> <style>
>> DG> a::before {
>> DG> content: attr(a1) "\A" attr(a2) "\A" attr(a3) "\A" attr(a4);
>> DG> }
>> DG> </style>
>>
>> <style>
>> record1::before { content: attr(name) attr(surname) }
>> record2::before { content: attr(name) attr(surname) }
>> </style>
>> <body>
>> <record1 name= surname= >
>> <record2 name= surname= >
>> </body>
>>
>> This way don't allow to specify styles for visualization of these
>> attributes
>> (like the following)
>
> Sure it does.
>
> record1::before {
> content: attr(name) attr(surname);
> color: red;
> float: right;.
> /* ... */
> }
> record2::before {
> content: attr(name) attr(surname);
> color: blue;
> float: left;
> /* ... */
> }
>
> You've always been able to style generated content in some manner.
> CSS2.1 relaxed the restriction on display types and positioning as well
> to allow even greater flexibility.
Apparently Dmitry messed up his own example. Originally, he wanted to
use different colors for different attributes.
> Anyway, Isn't this best left up to the CSS WG? I don't think we have the
> authority to specify new CSS selectors.
Yep.
--Dao
Received on Friday, 18 May 2007 17:08:51 UTC