- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 24 Feb 2011 09:56:56 -0800
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: Brad Kemper <brad.kemper@gmail.com>, "Aharon (Vladimir) Lanin" <aharon@google.com>, W3C style mailing list <www-style@w3.org>
On Thu, Feb 24, 2011 at 9:48 AM, fantasai <fantasai.lists@inkedblade.net> wrote:
> On 02/24/2011 09:20 AM, Tab Atkins Jr. wrote:
>>
>> [snip]
>>>
>>> ul:rtl {
>>> list-style-image-transform: reflect(0deg);
>>> } /* or, transformation is automatic for directions not specified by
>>> author */
>>
>> This last one works for me too. There are only four image properties
>> in CSS, so having a separate transform property for them wouldn't be
>> onerous, I would think. We've talked about the usefulness of
>> transforming images before, too (rotation/scaling/skewing of
>> background images, particularly tiled ones, for example).
>
> "only four".. so far! Note that a property has very different
> cascading implications than an image() argument; be sure that's
> what you want. (It also uses more memory, since it requires
> extra storage per-element.)
Sure.
>> (While I'm usually in favor of image manipulation happening at the
>> <image> level rather than the property level, in this case it would
>> require repeating an image, which is fragile. Better for the author
>> to have transforms directly.)
>
> Oh, but variables should solve this problem! ;)
Don't make me spec the @image rule that's in my head!
~TJ
Received on Thursday, 24 February 2011 18:01:06 UTC