W3C home > Mailing lists > Public > public-web-perf@w3.org > April 2013

Re: [RequestAnimationFrame] ally: Separate capture & display cycles

From: Pablo Garaizar Sagarminaga <garaizar@deusto.es>
Date: Wed, 10 Apr 2013 10:45:35 +0200
To: public-web-perf@w3.org
Message-ID: <20130410104535.6e0c4d20@pc-garaizar>

On Tue, 09 Apr 2013 14:27:23 -0400
Philippe Le Hegaret <plh@w3.org> wrote:

> as I understand it, it wouldn't make any sense for the user agent to
> invoke RAF more than 60 times per second if the display is only
> capable of 60Hz. You might have a nice camera to capture your images
> but that won't give you automatically a nice display to watch them...

That's completely the key point: RAF provides a simple way to get the
best of the display you have (and prevents you from oversampling, which
is pretty cool BTW ;) ). 

The most important feature we should ask to RAF implementers is
stability, in order to miss no frames when presenting something at 60
Hz (or whatever the native frame rate it is).


  Pablo Garaizar Sagarminaga
  Universidad de Deusto
  Avda. de las Universidades 24
  48007 Bilbao - Spain

  Phone:       +34-94-4139000 Ext 2512
  Fax:                  +34-94-4139101
Received on Wednesday, 10 April 2013 08:46:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:35 UTC