Comment 1 for bug 1556407

I don't really think there is a bug, or at least I know why it's doing this: the delete operation is asynchronous, and doesn't return anything. To account for that, the client just does a stack-show after the delete, to return something to display. But at that point, the delete may not be already in progress.

Arguably we could remove that show, but can't because of compatibility.