Chess.com play hangs/ performance issues

I have had this issue for around the last month or so.

Microsoft Edge 120.0.2210.22

I can confirm that the issue does not arise on Chrome or the mobile application.

The 2 issues I am having are probably related (but I am not sure) - they are:

- On loading the play tab for the first time, the browser will hang.

- In analysis, engine analysis is not available (with evaluation and lines turned on) unless I manually change the selected chess engine. This affects every engine selected as far as I can tell.

It seems that chess.com has some issues loading the opening book/ engine due to a security issue.

From the DevTools I am getting this warning:

"Some resources are blocked because their origin is not listed in your site's Content Security Policy (CSP). Your site's CSP is allowlist-based, so resources must be listed in the allowlist in order to be accessed.
A site's Content Security Policy is set either via an HTTP header (recommended), or via a meta HTML tag.
To fix this issue do one of the following:
(Recommended) If you're using an allowlist for 'script-src', consider switching from an allowlist CSP to a strict CSP, because strict CSPs are more robust against XSS . See how to set a strict CSP .
Or carefully check that all of the blocked resources are trustworthy; if they are, include their sources in the CSP of your site. ⚠️Never add a source you don't trust to your site's CSP. If you don't trust the source, consider hosting resources on your own site instead."

It lists a number of affected resources but it seems some important resources are blocked because of this including "board-layout.client.XXXXXXX.js", "analysis.client.js", "stockfish-nnue-16.840e654f.js"

My suspicion is that this is some security policy that edge has added (I have tracking prevention and enhanced security set to strict) or that hasn't been pushed to chrome yet (noting that microsoft edge is built on chrome).

Steps taken to fix the issue (that do not work):

- Using safe mode.

- Clearing browser cache and reloading.

same here, if you manage to solve it, please let us know

This is possible but likely something Microsoft added on their own and unless Google is planning on adding it themselves, isn't something that would be pushed to Chrome.

I suggest using Help > Report a Bug and use that to link to this topic or copy/paste the above information into it. You should do it from Edge.