I see that everyone goes with the easy fix in GWT XML file.

What I think is best to be done is to take these two files: 
https://code.google.com/p/google-web-toolkit/source/detail?spec=svn10989&r=10989
 .

Make sure you keep the package names as the classes that these extend are only 
visible in the same package (default access).

Copy paste in your code with a different name, and add this to your gwt.xml: 

AFTER upgrading to GWT 2.5 this can be removed.

[CODE]
      
   
    
    <replace-with 
class="com.google.gwt.animation.client.AnimationSchedulerImplWebkitFix">
      <when-type-is class="com.google.gwt.animation.client.AnimationScheduler"/>
      <any>
        <when-property-is name="user.agent" value="safari"/>
      </any>
    </replace-with>


    <!-- Implementation based on mozRequestAnimationFrame -->
    <replace-with 
class="com.google.gwt.animation.client.AnimationSchedulerImplMozillaFix">
      <when-type-is class="com.google.gwt.animation.client.AnimationScheduler"/>
      <when-property-is name="user.agent" value="gecko1_8"/>
   </replace-with>[/CODE]

Basically the above code will patch your GWT 2.4 animation code to be on par 
with the GWT 2.5 code.

Correct me if I'm wrong.

Regards,
Alex.


On Monday, January 14, 2013 12:12:20 AM UTC+2, Craig Mitchell wrote:
>
> Thanks Andy!  Your workaround works great!
>
> +1 for not happy with Google!  GWT 2.4 is supposed to be the stable build! 
>  We've been deferring going to GWT 2.5 because we wanted the stability.
>
> Summary for workaround is to add the following to your .gwt.xml file:
>
> <!-- TEMP FIX UNTIL GOING TO GWT 2.5 -->
> <!-- Fallback implementation, based on a timer -->
> <replace-with 
> class="com.google.gwt.animation.client.AnimationSchedulerImplTimer">
>   <when-type-is 
> class="com.google.gwt.animation.client.AnimationScheduler"/>
>   <any>
>     <when-property-is name="user.agent" value="ie6"/>
>     <when-property-is name="user.agent" value="ie8"/>
>     <when-property-is name="user.agent" value="ie9"/>
>     <when-property-is name="user.agent" value="safari"/>
>     <when-property-is name="user.agent" value="opera"/>
>   </any>
> </replace-with>
>
> <!-- Implementation based on mozRequestAnimationFrame -->
> <replace-with 
> class="com.google.gwt.animation.client.AnimationSchedulerImplMozilla">
>   <when-type-is 
> class="com.google.gwt.animation.client.AnimationScheduler"/>
>   <when-property-is name="user.agent" value="gecko1_8"/>
> </replace-with>
> <!-- ************* END ************* -->
>
>
>
> On Saturday, January 12, 2013 5:20:20 AM UTC+11, Andy wrote:
>>
>> I posted the workaround that we're using to the chromium issue thread: 
>> http://code.google.com/p/chromium/issues/detail?id=158910
>>
>> We have 100s of customers with servers deployed behind firewalls so this 
>> is going to be ugly.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/bbBAcb2jfh4J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to