Set store.pageSize = 19 (or grid.height = 1200) in order to view the top of the dataset later on. This alteration is needed due to a different bug introduced in 4.0.2.
Click "add record". Note a new record is inserted at the top, and existing records shift down as expected. However, the sequence is numbered 1, 2, 2, 3, 4....
Scroll all the way down. The expected end index of 5001 is not there. If the end index is only 4994, that is due to a different bug.
Scroll all the way up. The newly added record at index 1 is no longer there. The original record at index 1 remains.
Optionally, you may choose to refresh the page before the next set of tests. It doesn't effect the outcome whether you do or not.
Click "remove record". Note the record at index 1 is removed as expected. Note that an empty space exists where the record at index store.pageSize + 1 is expected.
Scroll all the way down. Note the index is still 5000 (or 4994), not the expected 4999.
Scroll all the way up. The removed record at index 1 returns.
Refresh the page before the next set of tests.
Click "filter". Note only records with ratings 3 or higher are shown, as expected.
Scroll all the way down. Note the end index is still 5000 (or 4994) and unfiltered records are shown.
Scroll all the way up. Note the filter no longer applies.
In Firefox, it may not be possible to view the topmost record when scrolling back and forth.
The following sequence of steps will cause empty spaces to appear: 1-5 -> 11. However, filtering after a refresh works as expected.
The heart of the workaround at the moment is to manage the full set of records, filtered and unfiltered, outside of the grid and its store. Additions, removals and filtering are processed on the externally managed sets, then swapped into the grid's store.
The fix would be to have the grid's store properly update its prefetchData, snapshot and totalCount. However, that involves a complex sequence of scroller (verticalScroller docking/undocking) and grid view updates we are still investigating.
The set of issues are being brought to the framework developer's attention at this opportune time in the hopes these issues will be resolved by 4.0.2 final.