W3C home > Mailing lists > Public > www-style@w3.org > February 2011

Re: directional images

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 24 Feb 2011 09:20:57 -0800
Message-ID: <AANLkTikK4YA7EiRishkPKg4XU=h=c_frUDQu8X3HgXfC@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "Aharon (Vladimir) Lanin" <aharon@google.com>, W3C style mailing list <www-style@w3.org>
On Thu, Feb 24, 2011 at 7:58 AM, Brad Kemper <brad.kemper@gmail.com> wrote:
> On Feb 23, 2011, at 1:00 PM, Tab Atkins Jr. wrote:
>> <ul dir=rtl>
>>  <li>ONE</li>
>> </ul>
>> <style>
>> ul {
>>  list-style-image: image( url("right-facing-arrow.jpg"), ltr );
>>  transition: list-style-image .2s;
>> }
>> ul:hover {
>>  list-style-image: image( url("highlight-right-arrow.jpg"), ltr );
>> }
>> </style>
> The parentheses embedded in parentheses are kind of hard to read. This seems like a place where we should have a direction pseudo-class, and then just use a different image (or have  image transformation properties for list-style-images, border-images, etc.).
> 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).

(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.)

Received on Thursday, 24 February 2011 17:24:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:43 UTC