As a workaround (not a fix) we currently are excluding Edge from the CSP tests that need to interact with these external scripts in a certain way.

So we have the following:

All browsers except Edge + CSP + basic interactions with external scripts = Yes. Edge browser + CSP + basic interactions with external scripts = Yes. All browsers except Edge + CSP + complex interactions with external scripts = Yes. Edge browser + CSP + complex interactions with external scripts = No.

So we are covering CSP on all browsers including Edge, and we're doing basic interactions with the external scripts on all browsers including Edge. But for the CSP and complex interactions with those scripts, we do all browsers except Edge.

We're getting the coverage we need to ensure our complex interactions are good with those scripts because Edge is mostly just Chrome anyway, and we're getting all the CSP checks we need. So we know our code is good - and that's really what we're here to test.

We just have a combination of Next + CSP + Edge + External scripts outside our control when we're interacting with them in a complex way that is failing. It's just a test setup failure.

Any solution is really going to be some kind of command/parameter that forces the CSP to ignore the errors, and by skipping that rare combination in the test suite we're doing that already.