You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a rest based grid and do a remove on a selected row in the grid. The DELETE is executed on the store and the row is removed form the grid, but still the grid.selection is ponting to the removed row.
The code is very simple to reproduce:
on(document.getElementById("delete"), "click", function(){
for(var id in grid.selection){
var x = prompt("Do you want to delete id: " + id+ "? Type OK in the prompt field to confirm");
if(x==="OK")
restStore.remove(id);
}
});
This works fine the first attempt, but the next attempt, without selecting any new row, it still tries to delete the same row as before and actually a new DELETE is sendt to the rest store.
I think the bug is that grid.selection should be empty after the first delete.
The text was updated successfully, but these errors were encountered:
This should be resolved by #101; note however that we've also changed the nature of select and deselect events to fire a batch event passing an array of affected rows or cells, instead of firing many events each with a singular row or cell.
I have created a rest based grid and do a remove on a selected row in the grid. The DELETE is executed on the store and the row is removed form the grid, but still the grid.selection is ponting to the removed row.
The code is very simple to reproduce:
This works fine the first attempt, but the next attempt, without selecting any new row, it still tries to delete the same row as before and actually a new DELETE is sendt to the rest store.
I think the bug is that grid.selection should be empty after the first delete.
The text was updated successfully, but these errors were encountered: