Thanks for pointing this out - we've seen this off and on for many Chrome Beta versions since around 20 or so, but they always fix it before a stable Chrome is released. From that we have to assume that if a user isn't using a stable Chrome version, they are willing to accept unstable behavior.
From some brief analysis of the animations that are failing, I would note that our animations are using the GWT animation code - we don't re-implement the animation timing, but make use of the same code that is found in GWT itself. I would suspect then that this bug will be present in some other GWT animations, and that a fix must either be made in Chrome itself, or in GWT. While we might be able to help in producing such a patch for GWT, it might not be worth it if Chrome is going to keep changing how that animation code works.
Looks like this could be a bug related to this topic - the linked discussions of problems go back to May of this year, which seems to be about the time I started seeing reports of this breaking in Chrome from IRC. Indeed - the GWT Animation.update method is doing some bookkeeping to see if the animation ought to stop based on the value of the timestamp passed into the animation callback. This code is the same in GWT 2.4 and 2.5, as well as some other JS animation libraries.
We cannot wait for GWT or Chrome team to fix this. As we have a product released, that uses animations and as soon as Chrome will auto-update for our customers, incidents will start comming in with this.
Can you please elaborate on the possible solution described: "we could provide a fixed one (GWT Animation class) that you need to add to your classpath so its overriding the GWT one".
We are fine with overriding the GWT Animation class in order to fix this. We are using GWT 2.4.
When could this class be ready? We are thinking of releasing a fix for this issue, if there is one. So that our customers can use the webapp with Chrome.
Thanks for the updates - I've been watching a few other posts that are also reporting this in GWT itself. Once a fix is known, if it isn't available in a release, we can demonstrate how to patch it easily using GWT's rebind feature.
If for some reason you cannot use GWT 2.5, consider getting a copy to see the what code is in the Chrome-specific animation classes, and patching just those classes. I have not yet tested that, since there is a stable GWT release out there already with this fix, confirmed by multiple sources.