W3C home > Mailing lists > Public > public-fx@w3.org > October to December 2015

Re: [web-animations] Should computedTiming return a live object?

From: Brian Birtles <bbirtles@mozilla.com>
Date: Sun, 4 Oct 2015 11:44:14 +0900
Message-ID: <CAF-W_FQPpGrFQacmu8hP9Uq7Zz2bHOfkFYiUBoE_pFDZy+3Gtg@mail.gmail.com>
To: Domenic Denicola <d@domenic.me>
Cc: "public-fx@w3.org" <public-fx@w3.org>, "www-style@w3.org" <www-style@w3.org>, "public-webapps@w3.org" <public-webapps@w3.org>
On Sat, Oct 3, 2015 at 1:21 AM, Domenic Denicola <d@domenic.me> wrote:
> Anne's questions are interesting and worth answering. For example, which of these properties are typically held in memory already, versus which would require some kind of computation---the former usually are better as properties, and the latter as methods.

The timing properties are typically held in memory while the
computedTiming properties will typically be generated on-demand since
they can be calculated from the timing properties and some of them
change on each frame.
Received on Sunday, 4 October 2015 02:44:42 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 4 October 2015 02:44:43 UTC