I already primarily do use chrome (I am right now), not everyone does however, nor do users of the forums, and that initial message is often a very quick turn-off for them and they go away to not return (directly reported as such).
This old post here looks somewhat related:
https://meta.discourse.org/t/cannot-load-app-for-a-meta-topic/78008
The post at elixir forums about it (have to be logged in):
https://elixirforum.com/t/problem-with-elixirforum-content-error/14885
A pixls forum discussion (of which clearing the cache, which clears the webworker, fixed it, though who knows for how long):
Manjaro forum:
https://forum.manjaro.org/t/corrupted-content-error-on-firefox/56148
And loaded firefox in safe mode, navigated to https://meta.discourse.org/, site loaded, clicked login, clicked github, and the page that popped up in the little window was (after a flicker of it going through github):
Of which clicking
Try again and it worked.
So yes, I would love to hear of an idea to get everyone switched to a singular browser as it would make development so much easier in my day job, but that also sounds like stagnation waiting to happen… Until then, if you have any ideas for how to convince multiple non-dev, normal people to switch from their preferred browsers, especially when half the time they access the site then it will not load so they won’t come back anyway, I’m all ears.
Before posting this I tried a few more times in firefox, it seems that it loads fine in the main tab but when loading the github login page then on the redirect back from github it is doing that screen rather consistently. A potentially interesting screenshot:
Note how the site request never even appears as the service worker has hijacked it. When refreshing the page to continue then the service worker is performing a
fetch request, which then continues the pipeline properly.
Whether a firefox bug or not, it’s only affecting discourse sites on any URL even while running firefox in safe mode