Re: [fxtf-drafts] [css-motion] offset-* property names collide with logical properties

Was there a conclusion to this discussion?  Chrome has shipped support
 for the new names, although they still don't support the full spec.

I thought of it again while reading up on the Web Animations API.  As 
@birtles briefly [mentioned 
above](https://github.com/w3c/fxtf-drafts/issues/51#issuecomment-250090651):
 WAAPI uses `offset` in a keyframes set to indicate the timing offset,
 and they do it in a way that is syntactically indistinguishable from 
a CSS property named `offset`. *

Regardless, if the decision is to go with the current names, it would 
be nice to get a resolution & close this issue.  Or if the issue is 
open until the logical properties spec is updated, at least mark the 
resolution about the offset/motion property names.

_____________________________

* Short version of that conflict:

The following CSS keyframes:

```css
@keyframes {
20% {color: blue; opacity: 1}
70% {color: pink: opacity: 0.5}
}
```

can be written for WAAPI as:

```js
element.animate([ 
  { color: "blue", opacity: 1, offset: 0.2 },
  { color: "pink", opacity: 0.5, offset: 0.7 },
], duration);
```

Which happens to look an awful lot like how you'd try to write a 
keyframe animating an `offset` property.

And yes, this was perhaps a poor API design choice for that spec, see 
https://github.com/w3c/web-animations/issues/164 for discussion. But 
it's already shipped in 2 browsers.

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at 
https://github.com/w3c/fxtf-drafts/issues/51#issuecomment-280890090 
using your GitHub account

Received on Sunday, 19 February 2017 02:09:48 UTC