Re: [AnimationRequestFrame] Initial editor's draft of AnimationRequestFrame spec available from Boris Zbarsky on 2011-05-03 (public-web-perf@w3.org from May 2011)

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 03 May 2011 09:30:17 -0400
To: public-web-perf@w3.org
Message-ID: <4DC00369.3040109@mit.edu>

On 5/3/11 1:08 AM, James Robinson wrote:
> The words "normative" and "should" are mutually exclusive.  I agree that
> browser should (and likely will, regardless of what we do) schedule
> these callbacks to match the refresh rate of the display whenever
> possible, but text in a specification that uses the word "should"
> instead of "must" is by definition not a normative requirement.  We
> can't always promise that the callbacks will be invoked at the refresh
> rate of the display and so I feel this is a quality of implementation issue.

I think Jatinder's point is that the spec needs to make it clear that 
firing at the refresh rate is the desired behavior for this API.

-Boris

Received on Tuesday, 3 May 2011 13:31:19 UTC