- From: Brian Birtles <bbirtles@mozilla.com>
- Date: Thu, 17 Apr 2014 17:05:17 +0900
- To: Boris Zbarsky <bzbarsky@MIT.EDU>, public-fx@w3.org
(2014/04/17 15:36), Boris Zbarsky wrote: > On 4/17/14 2:13 AM, Brian Birtles wrote: >> We added computedOffset because some people commented that they wanted >> to be able to see how the UA was arranging their keyframes (since there >> is some auto-spacing behaviour). So it's output only. However, we also >> want to be able to allow authors to say, for example: >> >> animA.effect.setFrames(animB.effect.getFrames()); > > This would work if getFrames returned a sequence of dictionaries that > inherit from Keyframe, fwiw. So it doesn't require adding anything to > Keyframe. Ok, that makes sense. I've made this change: https://dvcs.w3.org/hg/FXTF/rev/bac24dfe38fd > In practice, this only matters if CSS adds a property called > "computedOffset", right? Yes, that's right. Perhaps we could leave it out until we need it? Thanks again! Brian
Received on Thursday, 17 April 2014 08:05:46 UTC