Bug 14609 - Interpolating 'other' value types should apply delay (and step timing functions if necessary)
Summary: Interpolating 'other' value types should apply delay (and step timing functio...
Status: NEW
Alias: None
Product: CSS
Classification: Unclassified
Component: Transitions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dean Jackson
QA Contact: This bug has no owner yet - up for the taking
Whiteboard: [postpone to next level?]
Depends on:
Reported: 2011-10-30 22:40 UTC by Dean Jackson
Modified: 2014-01-10 01:26 UTC (History)
6 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Comment 1 L. David Baron (Mozilla) 2012-02-17 01:21:19 UTC
I tend to think that at this point we should postpone this to the next level of the transitions spec.
Comment 2 Simon Fraser 2012-02-17 01:33:06 UTC
Comment 3 L. David Baron (Mozilla) 2012-02-24 00:24:34 UTC
Though, actually, now that I think about it a little more, waiting to do this might lead to compatibility problems.
Comment 4 Sylvain Galineau 2012-02-25 23:07:59 UTC
Also related to http://lists.w3.org/Archives/Public/www-style/2009Nov/0328.html
Comment 5 fantasai 2012-03-01 00:53:42 UTC
Wrt compatibility problems... could you make the default value of transition-property to be 'auto', and thus only transition interpolable properties by default? Then if you want non-interpolable properties to transition, you have mention them explicitly.
Comment 6 Sylvain Galineau 2012-03-01 00:56:09 UTC
There is no 'auto' value today; since we want to push this to LC and beyond, shouldn't we avoid introducing new values and change initial values?
Comment 7 L. David Baron (Mozilla) 2014-01-10 01:26:54 UTC
I think in http://lists.w3.org/Archives/Public/www-style/2012Nov/0261.html we decided to do this for CSS Animations but *not* for CSS transitions.  Though the minutes aren't incredibly clear.