Re: [csswg-drafts] [web-animations] Reject both "float" and "offset" in keyframes object (#4331)

Actually, this is already covered by the procedure to [process a keyframe-like object](https://drafts.csswg.org/web-animations-1/#process-a-keyframe-like-object). That has:

> 2. Build up a list of animatable properties as follows:
>     1. Let animatable properties be a list of property names (including shorthand properties that have longhand sub-properties that are animatable) that can be animated by the implementation.
>     2.  Convert each property name in animatable properties to the equivalent IDL attribute by applying the animation property name to IDL attribute name algorithm.
> 3. Let input properties be the result of calling the EnumerableOwnNames operation with keyframe input as the object.
> 4. Make up a new list animation properties that consists of all of the properties that are in both input properties and animatable properties, or which are in input properties and conform to the `<custom-property-name>` production.

It only ever does a `[[Get]]` on the animations in the resulting _animation properties_ list.

So in the test case here:
* _animatable properties_ will include `cssFloat` (but not `float`).
* _input properties_ will be [[`float`]].

So in step 4 _animatable properties_ should be empty.

So this appears to be a blink bug. @BorisChiou do you mind adding a WPT for it? Perhaps by adding `float` to `gNonAnimatableProps` in [`processing-a-keyframes-argument-001.html`](https://github.com/web-platform-tests/wpt/blob/master/web-animations/interfaces/KeyframeEffect/processing-a-keyframes-argument-001.html#L22).

-- 
GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4331#issuecomment-534332999 using your GitHub account

Received on Tuesday, 24 September 2019 00:10:38 UTC