Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0.3-core, 1.2.2-core
-
None
Description
When "first" property is set to -1, UIXIterator assumes that the row is not available and scrolls to the end. The logic is there to handle cases when some records have been deleted and "first" points to an index >= rowCount. However, we should not be applying this logic to a negative "first". Instead, it should be just set to 0.
The affected method is UIXIteratir._fixupFirst() (see provided patch)