Last Comment Bug 533352 - Support 'transition-delay' on non-animatable properties
: Support 'transition-delay' on non-animatable properties
Status: NEW
: dev-doc-needed
Product: Core
Classification: Components
Component: CSS Parsing and Computation (show other bugs)
: unspecified
: All All
-- enhancement with 4 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Jet Villegas (:jet)
Depends on:
Blocks: css-transitions 521890
  Show dependency treegraph
Reported: 2009-12-07 15:40 PST by d
Modified: 2016-07-23 13:03 PDT (History)
10 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image d 2009-12-07 15:40:36 PST
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; sv-SE; rv:1.9.3a1pre) Gecko/20091205 Minefield/3.7a1pre
Build Identifier: 

Based on:

I think we should do a "test implementation" of this with several properties, although the one I can see as most useful is the display property.

Reproducible: Always
Comment 1 User image David Baron :dbaron: ⌚️UTC-8 2009-12-07 21:04:51 PST
If we did a test implementation, it would be for all properties, based on the idea in bug 529934 comment 2, plus changes to the transition manager to handle transition-delay even when interpolation is not possible.
Comment 2 User image Daniel Gredler 2011-01-02 18:11:25 PST
I just wanted to chime in real quick with a user's perspective... I've been playing with transitions for the past week or so (for the Game On competition), and it would be very useful to be able to specify whether all-or-nothing, non-animatable changes (e.g. display:none <-> display:block) happen before or after other transitions take effect. Re-using the existing transition syntax makes sense -- I actually tried to use the transition-delay as proposed before digging into the MDC and W3C docs to find that this wasn't supported. You can see the sorts of hacks that are cropping up to work around this limitation here:

Note You need to log in before you can comment on or make changes to this bug.