- From: Steve Block <steveblock@google.com>
- Date: Mon, 6 May 2013 14:27:30 +1000
- To: Brian Birtles <bbirtles@mozilla.com>
- Cc: "public-fx@w3.org" <public-fx@w3.org>
Hi guys. Sorry I missed the meeting last week. A few comments ...
> Also, since there's no array shortcut (unlike Option 1), we can safely allow
> multiple properties. This makes the following possible:
>
> keyframeEffect.setFrames([{ left: '50px', top: '50px' }, { left: '100px',
> top: '100px' }]);
>
> ...
>
> Note that to set a per-value composite operation you have to use the full
> syntax.
>
> e.g.
>
> keyframeEffect.setFrames(
> [ { values: [ { property: 'left', value: '50px', composite: 'add' } ] },
> { values: [ { property: 'left', value: '0' } ] } ]
> );
How about we allow the value property to be a space-separated pair, eg
'50px add'? I think we could then do away with Keyframe and always use
KeyframeShortcut ...
keyframeEffect.setFrames(
[ { offset: 0.1, left: '50px add', top: '100px replace' },
{ left: '0'} ]
);
> ➙ With regards to the offset property, we prefer option (b)
I think I'd vote for (c): use 'keyframeOffset' to avoid the problem,
but I don't feel strongly and am happy with (b).
> Shane: I'm happy to go with this frame-based approach
Me too.
> ACTION: Steve to write design doc for media integration
On it
Steve
Received on Monday, 6 May 2013 04:31:13 UTC