developer.chrome.com | The frontend , backend , and content source code | Browser Plugin library

The element itself may exist. It's not semantically proper, but you can append to it instead, and it will apply the CSS rules as desired.

According to the link in the error message, this is due to a new security feature implemented in Chrome v92.

Chrome v92 is now requiring the Cross-Origin-Resource-Policy header in order to share resources between two or more origins. I assume you are trying to use a cookie or other resource set by api-dev.host.com and so you would need to implement the header or have your CORS configuration set to Access-Control-Allow-Origin: *.

If you do not have the Access-Control-Allow-Origin set to * you can set the Cross-Origin-Resource-Policy header using the following Nginx configuration:

You can debug via Eruda Console for Mobile Browsers
https://github.com/liriliri/eruda

We're as well facing issues with our signalR (WebSockets as transport). We're not able to reproduce it in our lab. The HAR files of our customer and extended logging provided us only the information that the client "consuming only after following interesting groups" is not sending pings within the default 30 seconds needed to keep the connection. Therefore the server closes the connection. We added logs in the signalR client library and only saw the ping timer not being hit on time. No error, no nothing. (Client is JavaScript and the issue occurred on customer site in chrome 87 (throttling was implemented there already for half of the chrome users - https://support.google.com/chrome/a/answer/7679408#87))

And the world is slowly getting aware of "an issue": https://github.com/SignalR/SignalR/issues/4536

Our quick help for our customers will be to create an ET with a manual broadcast ping-pong mechanism from the server site and each client will have to answer. Avoiding being dependent on the JavaScript ping in the signalR library until a "better" solution or fix is provided.

As the warning shows, Chrome will require cross-origin isolation starting version 91 in order to use SharedArrayBuffer. As far as I know there is nothing you can do to resolve the warning other then wait for a react update.

Others are also having this issue as you can see here and here

The issue is fixed in this pull request but has not yet been released.

Edit: It is now fixed in version 17.0.2 of react.

To run everywhere except "google" domains use exclude_globs. In manifest.json:

You'll need to set an environment variable to tell it to not use an inline script:

INLINE_RUNTIME_CHUNK=false

Add this to your .env file and when you rebuild the offending bit of React is placed into a file.

the feature is available from Chrome 91 (https://developer.chrome.com/blog/new-in-devtools-91/#memory-inspector).

At the moment, official Chrome release is 90. You can download Chrome Beta or Chrome Canary to use that feature!

It's a known bug, https://crbug.com/1117475.

Meanwhile use set instead of append in the value of operation.