Describe the bug
If the socket disconnects and you have pending changes, and the notebook can't save them for over 30s, you get an error toast the says "Unable to save changes." The notebook will keep trying to reconnect and save, and if it's successful, everything will be fine again. But, the error toast doesn't go away and the page still feels broken since it's still there.
To Reproduce
Steps to reproduce the behavior:
Make an edit to a notebook you own.
Get the notebook to not save somehow (in development, add an artificial delay to save events).
See the Unable to save changes error toast.
Wait for save/saveconfirm to complete successfully.
See toast not go away.
Expected behavior
After a successful save, it's confusing to leave the toast visible as it seems like something is still broken.
Screenshots
Desktop (please complete the following information):
macOS Safari 15.6.1
Describe the bug If the socket disconnects and you have pending changes, and the notebook can't save them for over 30s, you get an error toast the says "Unable to save changes." The notebook will keep trying to reconnect and save, and if it's successful, everything will be fine again. But, the error toast doesn't go away and the page still feels broken since it's still there.
To Reproduce Steps to reproduce the behavior:
Expected behavior After a successful save, it's confusing to leave the toast visible as it seems like something is still broken.
Screenshots
Desktop (please complete the following information): macOS Safari 15.6.1