It looks like the for the preloader is being blocked by Chrome.
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src https://forum.storj.io/logs/ https://forum.storj.io/sidekiq/ https://forum.storj.io/mini-profiler-resources/ https://storj-s3.bcdn.literatehosting.net/assets/ https://storj-s3.bcdn.literatehosting.net/brotli_asset/ https://forum.storj.io/extra-locales/ https://storj.bcdn.literatehosting.com/highlight-js/ https://storj.bcdn.literatehosting.com/javascripts/ https://storj.bcdn.literatehosting.com/plugins/ https://storj.bcdn.literatehosting.com/theme-javascripts/ https://storj.bcdn.literatehosting.com/svg-sprite/ 'report-sample' 'sha256-rwfdvotzygqmkowfnaex564b66behoel4+grlgqughg=' https://storj.ideas.aha.io https://secure.aha.io/assets/idea_portals/embedded/application.js https://lcstorj-92e2.kxcdn.com https://www.redditstatic.com/ads/pixel.js https://storj.bcdn.literatehosting.com". Either the 'unsafe-inline' keyword, a hash ('sha256-rwfDVOTzygQmkOwFNAeX564B66beHoel4+gRLgQUgHg='), or a nonce ('nonce-...') is required to enable inline execution.
Did you install this as an App in Chrome? That’s likely the issue. The Content Security Policy for Chrome Apps is causing this. Chrome has stopped support for Chrome Apps
That all being said, it’s better to not use inline javascript and instead reference the script as a separate file to avoid these kinds of things.
This is in Discourse Core, so it’s nothing about this site. Since Chrome Apps are going away, I suspect that the Discourse developers don’t care much about supporting them. That said, this loader is a new feature and it’s a good bet that they intend to move that code to a script Real Soon Now (unless there is some reason not to?). That’s the kind of thing that they are generally quite careful about, so I suspect that either there is some reason that they are doing that (like after the site loads that gets removed?) or it’s a placeholder while they tweak other things about the feature.
I haven’t installed it as a chrome app. I did just go into the apps chrome://apps and removed JamStash, and the website now works fine… Not entirely sure if removing that was related since I didn’t try the site immediately before removing it today.
It’s not caused by anything on your site, so it’s in Discourse core. I haven’t seen any similar reports on meta.discourse.org, so my guess is that JamStash was the issue, however unlikely that may seem.
