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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 14 Dec 2011 10:49:17 -0800
Message-ID: <CAAWBYDAfSBOEWVX2BkYMwBXJ-V_WrDQzOG+toEAMRS_Nj_xiGg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style@w3.org
On Wed, Dec 14, 2011 at 10:18 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 12/14/11 10:47 AM, Tab Atkins Jr. wrote:
>> Right; I understood your meaning.  My point was that, if
>> 'display:none' prevents a transition from starting, then it *always*
>> prevents a transition from starting.  Having it as part of the start
>> state should suppress everything, because the "is the element
>> 'display:none' at this point?" check succeeds.  There is no situation
>> where 'display' switches from the start-state to the end-state,
>> followed by 'margin' (or anything else) switching from the start-state
>> to the end-state.  There's just a big bag of properties that change at
>> the same time.
> In actual implementations, you can have a situation where "display" switches
> from the start-state to the end-state but 'margin' doesn't do anything at
> all because the computation of its value is lazy (and in particular, it had
> no start-state, and may not have an end-state).
> Just fyi.

Yup, which is a good reason why Transitions should act like Animations
and not start if the start-state was display:none.

Received on Wednesday, 14 December 2011 18:50:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:08 UTC