-
13 Jul 2012 3:22 AM #21
It's an ExtJS Issue, since it's present in it's severe form only in ExtJS - other JS frameworks that can display huge tables don't have this problem.
-
13 Jul 2012 3:32 AM #22
i've changed the firefox set up like i said and it's working great...i don't know for sure why but it's working.
-
13 Jul 2012 4:19 AM #23
this has been fixed in extjs4.1.1
-
13 Jul 2012 4:21 AM #24
I was using ext js 4.1.1 when I had this problem ...
-
13 Jul 2012 8:08 AM #25
hm,
very interesting, because for me this problem has gone after upgrading to 4.1.1
-
13 Jul 2012 5:52 PM #26
4.1.1 has some improvements to optimize how the scroll synchronization works, however enabling smooth scrolling still introduces a bit of lag, there's not a whole lot we can do about it.
Evan Trimboli
Sencha Developer
Twitter - @evantrimboli
Don't be afraid of the source code!
-
13 Feb 2013 3:50 AM #27
Hi guys, while upgrading project to ExtJs 4.1.1a version, I discovered that grids scrolling and general performance is pretty low. In my case it was reproduced only on my Windows 7 PC on Firefox 18.0.2. Problem is connected to enabled "hardware acceleration". In 18.0.2 version "hardware acceleration" is enabled by default. When I turn it off, performance increased a lot. Issue with firefox was solved in firefox 19 beta, grid performance is much better.
But after check on other PCs, I found the same issue on OS X 10.8.2 Build 12C3006, Safari Version 6.0.2 (8536.26.17).
Checked ExtJS 4.2.x beta, grid performance is on the same level.
When you check the same grids in 3.x version, performance is fine.
Issue is not related to my application, as the same speed of scrolling is in extjs examples http://cdn.sencha.com/ext-4.1.1a-gpl...l-editing.html. Checked it Windows 7 firefox 18.0.2 and OS X 10.8.2 Build 12C3006, Safari Version 6.0.2 (8536.26.17)
Before writing this post I've made pretty big research, as I can not upgrade to 4.x version until grid scrolling is fixed. Maybe someone knows any improvements, that sencha team can advice? or should we expect better performance in next versions?
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-6481
in
4.1.


Reply With Quote