Re: content: url() is bad

Ian Hickson wrote:
> How about actually putting it all on one property, like this:
> 
>    'content'
>    Values: [ <uri> [ ',' <uri> ]+ '/' ]? [ <content-list> [ ',' <content-list> ]+ | normal

So the semantics are "stuff before '/' replaces, stuff after '/' becomes 
kids"?  And if I just want an image inside my h1 I would do:

   h1 { content: url(whatever) }

and if I want it to replace I do:

   h1 { content: url(whatever) / contents }

and this incidentally _forces_ me to include a fallback of some sort for 
the replacement URL?

I kinda like it, actually.

-Boris

Received on Wednesday, 14 April 2004 23:09:02 UTC