Am 21.01.2013 um 06:17 schrieb Brian Slesinsky skybr...@google.com:
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
What do you mean by too harsh? I haven't tested yet, but it seems
unlikely that any users would care if we dropped a few frames in a dialog
animation in an enterprise app. (Yes, of course gamers would care, but
that's a separate audience.)
Sorry but if you choose to animate things then
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:
Brian Slesinsky has uploaded a new change for review.
https://gwt-review.googlesource.com/1780
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
Goktug Gokdogan 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.
