Ext version tested:Browser versions tested against:Description:
I have an infinite grid with a huge amount of rows (> 1M), no filters, checkbox selection model, sorting is done on the server. If I scroll down to any page using either pagedown key or scroll bars, a correct page is fetched from the server and displayed. If I need to refresh the grid, such as after some Ajax-driven server-side operation, I execute grid.getStore().load(). Instead of loading the currently displayed page, or one of the pages that I would think would be in PageMap's cache, the refresh operation always loads page #1 from the server, so the current page effectively is not being displayed.
I've added some debugging console.logs, and it would seem that the store's currentPage is always 1, as opposed to what I think should be the current page. So, it would seem to me that when i'm scrolling the grid, that variable is not being updated properly, hence the subsequent load() calls also don't refresh the right page.
I've tried manipulating various PageMaps variables, using view.refresh() and store.reload() instead of store.load(), but the bottom line is that didn't help and my understanding is that load() should refresh things properly, at least it did in 4.0.7.
Initial grid load:
Scrolling down to any page:
Calling store.load(), which should call page=105 if i understand it right:
A console.log of grid.getStore().currentPage right before the load() call prints 1.
Am I doing something wrong or is this a bug? Is currentPage perhaps only applicable to paged grids and not infinite grids and if so, what's the proper way to refresh the infinite grid?