It seems like browsers (Firefox at least) cache quite aggressively and make the following possible:
Ensure you have default browser settings (i.e., cache is not disabled).
Open a task in the editor.
Create a new file with example content and save it.
Use the browser back button to go to previous page.
Use the browser forward button to return to the editor.
Expected result: the new file is visible.
Actual result: the new file isn't visible, user must refresh the page.
In the browser console I can see that the cached version is used, which is somewhat expected. However, it's surprising that it doesn't execute the JS to initialize the tab bar. Possibly, I can work around this by settings extrem anti-caching headers on the editor and the checkpoint view.
It seems like browsers (Firefox at least) cache quite aggressively and make the following possible:
Expected result: the new file is visible.
Actual result: the new file isn't visible, user must refresh the page.
In the browser console I can see that the cached version is used, which is somewhat expected. However, it's surprising that it doesn't execute the JS to initialize the tab bar. Possibly, I can work around this by settings extrem anti-caching headers on the editor and the checkpoint view.