UI Test loads with no view mode in Chrome

[davidmehren]

Description After pasting https://ui-test.hedgedoc.org/n/features into the Chrome Omnibox, the frontend only shows a big black box: The dev tools show a variety of messages: This behavior persisted over multiple reloads with cache disabled.

Manually selecting the "both" view mode switched to the correct mode after a short delay and caused two more warnings:

After that the issue was not reproducible anymore.

To Reproduce

1. Open the UI test in Chrome
2. ...be lucky?

Expected behavior The frontend shows one of the three view modes without the user having to manually select one.

Your Setup:

• OS: Arch
• Browser with version
  • Chrome 89.0.4389.90
• HedgeDoc version
  • dev-35b548d

[mrdrogdrog]

I tested it with exact this browser version aaaand.. can't reproduce. Something must be wrong with your setup.

[mrdrogdrog]

For a short time we had a broken service worker. Check if it is still registered in your browser (dev tools > Applications > Service Workers > unregister every service worker there)

[ErikMichelson]

This likely happens because we changed editorConfig local-storage syntax from editorMode: 1, 2, 3 to editorMode: view, both, edit. Clear your local-storage and try it again.

[mrdrogdrog]

@ErikMichelson maybe we should change the fallback. And write it back if we use it.

[ErikMichelson]

Well we currently do not verify the data at all (return JSON.parse(stored) as EditorConfig). I doubt that we really need to test each property - especially as this problem only appears for regular ui-test users. Also note that once you select one of the editor modes, the locally stored config will be corrected.

[mrdrogdrog]

Yes, but a type cast doesn't verify the data we read. I think it would be better to check the data for plausability.

[ErikMichelson]

For API response data validation we're tracking the progress in hedgedoc/hedgedoc#2910. As this seems to be solved, I'm going to close this now.