W3C home > Mailing lists > Public > www-style@w3.org > September 2010

Re: Proposal for CSS3.5

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 1 Sep 2010 10:17:11 -0700
Message-ID: <AANLkTi=y11=Ruh_ezW6c0Q3p0gpzXu7GiMOcfs+qSjcC@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: Alexander Shpack <shadowkin@gmail.com>, www-style@w3.org
On Wed, Sep 1, 2010 at 9:22 AM, Brad Kemper <brad.kemper@gmail.com> wrote:
> The problem you describe is more general than just backgrounds; it is a similar situation for any property that takes a comma-separated list (including box-shadow, for instance).
>
> A solution I would like to see that does not involve constants or variables would be to be able to leave blank spots in the list (astride the commas) to be able to leave those slots unchanged. So for instance, this:
>
> .twoClass { background-image: , url(other.png), ; }
>
> ...would change the second image only, and keep the other two from whatever they were before in the cascade. Essentially, keeping them as if you had retyped them in yourself. If there was a fourth item on the list, the above rule would still override that image, because of the number of commas.

Or even better, just some explicit way to target a particular subitem
of a list.  I don't like implications about "keeping things".

.oneClass { background-image: url(one.png), url(two.png), url(three.png); }
.twoClass { background-image[1]: url(other.png); }

~TJ
Received on Wednesday, 1 September 2010 17:18:03 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:31 GMT