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

Re: [css3-transitions] faster reversing of partially completed transitions

From: David Singer <singer@apple.com>
Date: Tue, 24 Nov 2009 17:08:07 -0800
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "L. David Baron" <dbaron@dbaron.org>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <706DD1DD-6B71-45C2-9DDB-CE69A434689A@apple.com>
To: Brad Kemper <brad.kemper@gmail.com>
It sounds like you want asymmetric behavior (transition in, abrupt out) whereupon the rule that Dean wrote wouldn't apply.  It's only in the case where you transition each way and you interuupt the forward to go back again, that most people expect it to back down in the same amount of time as it has taken so far to come up, as it were.

I think a 'guess of intentions' is needed here.  I think the duration has to be 'right' (shorter);  whether the function has to be perfectly reversed I am less clear.  And delays confuse me.

On Nov 24, 2009, at 16:47 , Brad Kemper wrote:

> On Nov 24, 2009, at 2:28 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
> 
>> If I'm going to be using an asymmetric timing
>> function for state transitions, though, as an author I'm going to
>> expect that they *always* run in reverse when the state transitions
>> back to 'normal'.  This includes transition-delays.  I'm not thinking
>> of the transition from :link to :hover to :link as two independent
>> changes, I think of them as being a change and then a reversal of that
>> change.
> 
> But you could think of them as two independent changes, and set the transition on each. I think that would be better than the UA trying to guess your intentions. I don't think I would expect it to run in reverse, unless (possibly, and that's the question) it hadn't finished running in forward. If you didn't set the :link version (or the no pseudo-class version), then unhovering would cause an abrupt change back. If that's what you wanted (and sometimes it might be), you'd be done; if not, you'd notice pretty quick and know what to do to fix it.
> 
> I can imagine, for instance, wanting a tooltip thingy that faded in (with opacity) after a second or two delay when hovering, and then disappearing to opacity:0 abruptly as soon as I moved the cursor away. If it was only half opaque, I would want the change back to be just as abrupt (with no delay or duration) as it would have been if the first transition had played out. I would expect that to happen if I didn't set any transition values on the :link, because the initial transition-duration without me setting it would be 0.   

David Singer
Multimedia and Software Standards, Apple Inc.
Received on Wednesday, 25 November 2009 01:08:49 GMT

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