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

Re: [css3-transitions] Transitions from display:none

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 17 Apr 2012 21:42:38 -0400
Message-ID: <4F8E1C0E.6050003@mit.edu>
To: James Robinson <jamesr@google.com>
CC: "Tab Atkins Jr." <jackalmage@gmail.com>, Sylvain Galineau <sylvaing@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
> I don't think my proposal is nearly that heavyweight.

OK, it's possible that I'm mixing up the various proposals.

> Here it is again,
> see http://lists.w3.org/Archives/Public/www-style/2012Jan/0816.html for
> the fuller context:

OK.  This seems somewhat reasonable, yes.  The task basically needs to 
save off the before/after change values (the ones that led to the 
browser noticing a change in the first place).

One issue here is that the transition start would be async, so either 
there will be a lag between style change and start or the start event 
will fire at time != 0 in the transition.  Maybe that's OK; it's not 
like timing of transition starts is so precise anyway.

> Concretely with this proposal in Sylvain's example the transition would
> not occur in either of the scenarios he mentions:
>
> e.style.color = "blue";
> e.style.display = "block";

Why would there be no transition in this case?

> e.style.display = "block";
> e.style.color = "blue";

Or in this one?

> or in this slightly trickier one:
>
> e.style.color = "blue";
> document.body.offsetTop; // forces a style flush, at least in WebKit
> e.style.display = "none";

This one is explicitly covered by your proposal, yes.

-Boris
Received on Wednesday, 18 April 2012 01:43:08 GMT

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