GWTCanvas's strange behavior(It should be IE's problem): timer driven animation frozen when move the mouse. (in IE, also happen when directly write vml markups)

[GoogleCodeExporter]

What version of gwt and gwt-incubator are you using?

What OS and browser are you using?
Windows XP and  IE (or IE core browser)

Do you see this error in hosted mode, web mode, or both?
both! even in VML native script without(GWT)

Here is the experiment and result (both GWTCanvas code and directly 
written VML code behave the same way ): 
1. make small(the size of the shape) and simple(the path string is 
short) shape: animation is fast without any doubt, even when keeping 
mouse moving. 
2. make small and complex shape:animation is fast, even when keeping 
mouse moving. 
3. make large and simple shape: animation is fast, but when keeping 
mouse moving over the shape, the animation stop. 

It should be the problem of M$. What puzzle me: what does
the mouse-move event have to do with the timer event for the 
animation. There are two guesses: 
1) mousemove event is of more priority than timer event in IE. 
2) When mousemove event trigged, IE will do some time-consuming things 
(specially when the shape is large) even you didn't write any code in 
javascript(or GWT's event handling function) to handle the event. The time-
consuming thing may be some repaint job done in IE when moving the mouse.

Workaround if you have one:
When using VML or its wrapper, Try to keep your shape screen size(at 
most). If it is larger than screan size, only draw the shape inside 
screan. DON'T count on IE to do the repaint in a suitable way.

Original issue reported on code.google.com by WChunm...@gmail.com on 5 Dec 2008 at 1:09

[GoogleCodeExporter]

Original comment by ecc%google.com@gtempaccount.com on 11 Dec 2008 at 9:23

[GoogleCodeExporter]

This is not a GWTCanvas issue.

From the description it seems to be an Animation issue on IE. He may be using 
an older version of GWT that did 
not guarantee an onUpdate(1.0) for animation completion.

Original comment by jaime...@google.com on 11 Dec 2008 at 9:28

[GoogleCodeExporter]

Original comment by jaime...@google.com on 2 Mar 2009 at 4:36

• Changed state: Invalid