One major issue…if the user makes changes to an editable livegrid and then scrolls so far that it causes additional rows to be fetched from the store, then all of the user’s (possibly exhaustive) unsaved edits are lost without warning.

Rather than hack in some kind of warning (which will only irritate the user who is trying to scroll or re-sort), can you simply cache the modified rows in “a linked-list of unsaved edits” so when the user scrolls those rows back into view, your code pulls the unsaved edits back from the linked-list overtop of whatever came back again from the store (so long as the “version” on the store does not change)? It’s 2 seconds of code (just walking list of dirty rows in grid, toss them onto list right before a load-from-store and likewise, pulling any dirty rows by number right after a load-from-store when the version number comes back the same) —and the benefit is that it makes LiveGrid make sense for editable grids!