Baseline Widely available
The securitypolicyviolation
event is fired when a Content Security Policy is violated.
The event is fired on the element when there is a violation of the CSP policy.
This event bubbles to the Window
object, and is composed.
Note: You should generally add the handler for this event to a top level object (i.e., Window
or Document
). While HTML elements can technically be the target of the securitypolicyviolation
event, in reality this event does not fire on themâfor example, a blocked <img>
source directly triggers this event on document
as the target, instead of bubbling from the <img>
element.
Use the event name in methods like addEventListener()
, or set an event handler property.
addEventListener("securitypolicyviolation", (event) => { })
onsecuritypolicyviolation = (event) => { }
Event type Examples Listening for securitypolicyviolation on Window
The code below shows how you might add an event handler function using the onsecuritypolicyviolation
global event handler property or addEventListener()
on the top level Window
(you could use exactly the same approach on Document
).
window.onsecuritypolicyviolation = (e) => {
// Handle SecurityPolicyViolationEvent e here
};
window.addEventListener("securitypolicyviolation", (e) => {
// Handle SecurityPolicyViolationEvent e here
});
Specifications Browser compatibility See also
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3