Thomas Broyer has posted comments on this change.
Change subject: Stop using prefixed API's in AnimationScheduler by default.
Firefox and Safari will use the Timer-based implementation. For Chrome we
can use requestAnimationFrame because it's unprefixed starting in Chrome 24.
Not using the most efficient implementation by default seems overly
harsh and likely to bias people against using GWT, so I tend to side
with making the efficient one the default. Javascript programmers
would usually react differently, by doing capability tests, and
selecting the appropriate
On Sun, Jan 20, 2013 at 8:25 PM, Ray Cromwell cromwell...@google.comwrote:
Not using the most efficient implementation by default seems overly
harsh and likely to bias people against using GWT, so I tend to side
with making the efficient one the default. Javascript programmers
would usually
On Sun, Jan 20, 2013 at 7:35 PM, John A. Tamplin j...@jaet.org wrote:
I agree, plus I think if we are going to do this there should be a more
global deferred binding property like useExperimentalApis in core.
What do you think about flags to turn on each prefixed symbol separately:
