Sluggish mouseover effect tree/grid

[mankz]

There's way too much processing going on when moving the mouse over a tree or grid. If I record half a second of moving my mouse over a row or two, I see _thousands_ of function calls logged in the FB profiler. Try this in Chrome, you'll see a noticeable lag with the row hover effect - which is insane, considering it's Chrome, and a Tree with 10 rows. Only option seems to be to disable trackOver to avoid the poor impression.

[Animal]

It's not slow. It delays actually setting the class until the mouse movement settles

If you are scrolling quickly it will not frantically add and remove classes (each of which will cause a layout)

[mankz]

It's _perceived_ as extremely sluggish. Do a side by side with 3.x and you'll feel it, huge difference. Couldn't the hover effect just use good old :hover for good browsers to save all the event firing?

[mankz]

[Animal]

Well that's possible. But trackMouseOver adds a class and fires events which form part of an API which is in wide use.

If all you need in your app is a hover state, then you could use

    trackMouseOver: false

and add

.x-grid-row:hover .x-grid-cell {
    background-color: whatever;
}

[mankz]

Just saying, my guess is that a newcomer to Sencha/Ext may perceive the 4.2 hover delay as a poorly performing grid.

[jchau]

Well that's possible. But trackMouseOver adds a class and fires events which form part of an API which is in wide use.

If all you need in your app is a hover state, then you could use

    trackMouseOver: false

and add

.x-grid-row:hover .x-grid-cell {
    background-color: whatever;
}

This doesn't work for locking grids since there's two separate grids...