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

Re: [css3-transitions] Interpolating images

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 30 Nov 2010 13:58:10 -0800
Message-ID: <AANLkTi=G0nNQRv-CZ=Kng4A9spN+S-1Bn4RCo2OR-u_Q@mail.gmail.com>
To: robert@ocallahan.org
Cc: Simon Fraser <smfr@me.com>, www-style list <www-style@w3.org>
On Tue, Nov 30, 2010 at 1:35 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Wed, Dec 1, 2010 at 10:30 AM, Simon Fraser <smfr@me.com> wrote:
>> Let's not start assuming that GPU acceleration is available everywhere.
>> It's
>> going to be a few years before GPU acceleration is widely available on
>> mobile devices,
>> and different browsers have different levels of support for GPU
>> acceleration.
>
> I'm just saying, let's not design new CSS features around implementation
> characteristics that are likely to go away in the medium term. Especially
> performance characteristics.
>
> (Plus, animated image size changes are already common, and engines already
> need/want to be able to do them fast.)

While we're on the subject, how about relaxing the restriction on
image-orientation that it only be multiplies of 90deg?  By the same
argument, implementations already have to handle this with rotate
transforms, and they'll want these to be fast.  The only difference is
that image-orientation is layout-affecting, so I'd just define the
size of the image to be the minimum-sized axis-aligned bounding-box
around the rotated image.

~TJ
Received on Tuesday, 30 November 2010 21:59:02 GMT

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