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

Re: directional images

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 23 Feb 2011 12:42:25 -0800
Message-ID: <4D657131.5050404@inkedblade.net>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: "Aharon (Vladimir) Lanin" <aharon@google.com>, W3C style mailing list <www-style@w3.org>
On 02/23/2011 11:27 AM, Tab Atkins Jr. wrote:
>
> There are a few possibilities that come to mind immediately:
>
> 1. Modify the syntax of the properties that accept images
> (background-image, border-image, list-style-image, cursor) to accept a
> directionality keyword which declares the directionality of the image.
>   (Roughly what Aharon suggested above, but using "ltr | rtl" instead
> of "rtlflip".)
>
> 2. Add a function which takes an image and declares a directionality
> for it, like "imagedir(ltr | rlt,<image>)".  (What's the
> directionality of an image produced from other images, like with the
> cross-fade() function?)
>
> I like the elegance of #2, because I think an image is directional or
> not, regardless of where it's used, but the composition problem
> troubles me.  I don't really want to have to lazily-create composed
> images so we can do necessary flipping of the component images based
> on the directionality of use, particularly if an image is assigned to
> a variable first and only later used in a property.
>
> So, I think #1 is the better solution here.
>
> Thoughts from implementors?

I'm not an implementor of this type of stuff, so you might not care about
my opinion, but I think adding an argument to the image() function makes
way more sense, given the universality of the concept.

~fantasai
Received on Wednesday, 23 February 2011 20:43:03 GMT

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