-
Type:
Bug
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: TM Maintenance
-
Critical
-
FIXED: problems with distinction between automatic and user scrolling
-
Emptyshow more show less
Problem:
from time to time the following error happens on scrolling and/or loading segments:
ext-modern-all-debug.js?_dc=1744648977270:2243 Uncaught Error: Top-most item should be positioned at 0 not 218.62799999999993
at new Ext.Error (ext-modern-all-debug.js?_dc=1744648977270:2195:21)
at Ext.Error.raise (ext-modern-all-debug.js?_dc=1744648977270:2243:23)
at Ext.raise (ext-modern-all-debug.js?_dc=1744648977270:2268:21)
at constructor.positionItemsTopDown (ext-modern-all-debug.js?_dc=1744648977270:115467:25)
at constructor.positionItems (ext-modern-all-debug.js?_dc=1744648977270:115337:23)
at constructor.syncRows (ext-modern-all-debug.js?_dc=1744648977270:116140:16)
at constructor.syncRowsToHeight (ext-modern-all-debug.js?_dc=1744648977270:116253:20)
at constructor.resync (ext-modern-all-debug.js?_dc=1744648977270:115670:24)
at constructor.doRefresh (ext-modern-all-debug.js?_dc=1744648977270:114954:24)
this happens because of not enough good distinction between the scrolling initiated internally as a result of adding/removing dummy placeholder record 'Loading ...' and the scrolling initiated manually by user via pulling the scrollbar down and/or via the mouse scrolling wheel, and those concurrent operations are broking the grid rendering internally.
Solution:
better distinction logic should be implemented, so that loading next batches of segments should be triggered only on manual scroll initiated by users