Success! Looks like we've fixed this one. According to our records the fix was applied for
a bug in our system
a recent build.
18 Feb 2013, 11:29 AM
I'll talk to Don some more about this. The 20ms setting feels about right. Have you tried it?
18 Feb 2013, 11:32 AM
20 is decent, still doesn't feel like Chrome (any delay is noticeable).
Btw, setting it to 0 produces an error...
18 Feb 2013, 11:41 AM
That's a bug for sure. I'll create a ticket.
var me = this,
onMouseOverOut = me.mouseOverOutBuffer ? me.onMouseOverOut : me.handleMouseOverOrOut;
* We need to make copies of this since some of the events fired here will end up triggering
* a new event to be called and the shared event object will be mutated. In future we should
* investigate if there are any issues with creating a new event object for each event that
* is fired.
Reducing the buffer to 20ms seems to feel pretty good - the problem with no delay is that it actually creates a real CPU hit to try to keep up with every mousemove. The delay was added because users on (cough) IE (cough) reported the CPU spike. We'll see how the new delay feels.
Of course you (or someone else reading this) can override this in your app
Thanks for reporting it - let us know how the smaller buffer value feels?
I see my window was stale when I posted my response :P
I guess we just need an Ext.support.EyeCandy feature detector
This doesn't work for locking grids since there's two separate grids...
Originally Posted by Animal
The :hover approach will make IE7 truly suffer.