Is your feature request related to a problem? Please describe.
It's frustrating to have to unload the doc (using the "X" button in the top right-hand corner) and fetch it again in order to have an up-to-date doc.
This is especially annoying when working on updates of the doc, but is also a problem when the server evolves and the clients don't realize they are out of sync forever.
Describe the solution you'd like
At page load, use the local storage to have a quick cached doc appear, but trigger a fetch action in the background anyway.
If the action succeeds, we should seamlessly replace the doc in the redux state without changing the route, so that the user's navigation is not disturbed, but the doc is updated anyway.
If the action fails for some reason, keep the cached doc, but maybe display a warning somewhere saying that this is an offline doc and may be out of sync
Is your feature request related to a problem? Please describe. It's frustrating to have to unload the doc (using the "X" button in the top right-hand corner) and fetch it again in order to have an up-to-date doc. This is especially annoying when working on updates of the doc, but is also a problem when the server evolves and the clients don't realize they are out of sync forever.
Describe the solution you'd like At page load, use the local storage to have a quick cached doc appear, but trigger a fetch action in the background anyway.