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

Re: animate/transition height to/from auto

From: Rik Cabanier <cabanier@gmail.com>
Date: Mon, 26 Nov 2012 10:03:25 -0800
Message-ID: <CAGN7qDBtM-3FWKONUHBL1fsyUnKrJxff2wQnodJnM8DeD_j-7Q@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, www-style list <www-style@w3.org>
On Mon, Nov 26, 2012 at 9:36 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Sat, Nov 24, 2012 at 11:10 AM, Rik Cabanier <cabanier@gmail.com> wrote:
> > I'll correct my previous statement:
> >
> > I think transitions should happen with resolved values.
> You really don't.  "resolved value" is a legacy hack, defined just to
> make it easier to talk about getComputedStyle().  It's incredibly
> inconsistent; a handful of properties from 2.1 return their used
> values, while all other properties return their computed values,
> including ones that act similarly to 2.1 properties.

I agree about the hack. I got very confused because I assumed that
'getComputedStyle' would return the 'computed value'.
Maybe the css 2.1 spec should change so it no longer uses 'computed value'.
If someone then talks about 'computed value',  you'd know that they are
using the obsolete definition.

I believe people would want the transition to happen between the values
that 'getComputedStyle()' returns (whatever that is called).
This site seems to emulate animation to 'auto' that way:

> > This thread started of with users asking for this feature so it would be
> > nice if we can come up with some level of support which can be
> implemented
> > and documented.
> I agree that it would be great.  But it's not trivial. ^_^

Nothing that involves layout is :-)
Received on Monday, 26 November 2012 18:04:00 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:22 UTC