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 22572 - Spec does not handle null property values in keyframes
Summary: Spec does not handle null property values in keyframes
Status: RESOLVED FIXED
Alias: None
Product: FXTF
Classification: Unclassified
Component: Web Animations (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: FXTF Web Animation bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-04 04:13 UTC by Steve Block
Modified: 2013-12-19 07:56 UTC (History)
1 user (show)

See Also:

Attachments

Description Steve Block 2013-07-04 04:13:16 UTC 
In section 6.17.2 'Normalizing a Keyframe object', step 10 sets 'property value' to' the result of calling toString on the name property of keyframe input.' but does not specify what to do if the name property is null.

Note before the KeyframeAnimationEffect is sampled, keyframes with unsupported property values are filtered out of the list of property-specific keyframes when normalizing the list of keyframes (6.16.4 step 6).

I think we should set 'property value' to null in this case, so the result of getFrames() will include the property and its value, but the offending keyframe will be filtered out before sampling.
Comment 1 Brian Birtles 2013-07-04 04:27:59 UTC 
Yeah, I think technically (according to ECMA5) toString.call(null) returns "[object Null]" but it's probably much more useful to have this an undefined result in an empty string.
Comment 2 Brian Birtles 2013-12-19 07:56:17 UTC 
Fixed: https://dvcs.w3.org/hg/FXTF/rev/5dc63e7ef62a