Demix securitypolicyviolation event from GlobalEventHandlers

[queengooborg]

This PR demixes the securitypolicyviolation event from the GlobalEventHandlers mixin.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[foolip]

Per https://w3c.github.io/webappsec-csp/#report-violation and https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/frame/csp/execution_context_csp_delegate.cc;l=287-294;drc=169c6cc102b39295a5bfe2f2a176b42b1c2fe2c4 the possible event targets are Element, Document and WorkerGlobalScope.

The entry on Element already exists, but can you add/update the other two to have matching data?

[queengooborg]

Are there any other changes that need to be made for this PR?

[foolip]

Yes, there are differences in the data across the 3 entries that need to be explained or fixed:

• Chrome 41 or 97?
• Edge 15 or 97?
• Firefox 63 or 93?
• Safari 10 or "preview"?

I would expect that the events on Element and Document were implemented at the same time, but maybe the event on WorkerGlobalScope came later.

Digging through source might be simpler than testing in this case.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[queengooborg]

I merged this PR while there were changes requested because I wanted to defer version number updates to a future PR so it wouldn't block the demixing of GEH. I do plan to follow-up on this using results from the collector!

[foolip]

I merged this PR while there were changes requested because I wanted to defer version number updates to a future PR so it wouldn't block the demixing of GEH. I do plan to follow-up on this using results from the collector!

Can you file an issue about this data? We can't trust the collector because it's based on the properties, and in particular the absence of changes suggested by the data doesn't imply that the questions in #16728 (comment) have been answered, so probably it will never come up organically from collector work.