This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14791 - Define the handling of 'initial' and 'inherit' in animation-name values
Summary: Define the handling of 'initial' and 'inherit' in animation-name values
Status: RESOLVED FIXED
Alias: None
Product: CSS
Classification: Unclassified
Component: Animations (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
URL:
Whiteboard: [medium]
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-11 20:24 UTC by Sylvain Galineau
Modified: 2013-02-08 00:14 UTC (History)
3 users (show)

See Also:

Attachments

Comment 1 Sylvain Galineau 2012-04-03 20:55:52 UTC 
If animation-property value is a list, do we treat initial and inherit as: 

1. unknown property names or...
2. treat the entire property value as invalid.

I would expect #1.
Comment 2 Sylvain Galineau 2012-04-10 22:05:15 UTC 
This is related to issue 2 marked in the Transitions spec: "Issue 2 Are ‘none’, ‘inherit’, and ‘initial’ allowed as items in a list of identifiers (of length greater than one)?"

This seems a rather significant and complex change at this stage.
Comment 3 Sylvain Galineau 2013-02-08 00:14:39 UTC 
It turned out there was no prose at all regarding inherit/initial being implicitly allowed as values for all the properties. Lifted the new section 2 from css3-flexbox.