W3cubDocs

/Web APIs

Element: securitypolicyviolation event

Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since ⁨October 2018⁩.

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.

Syntax

Use the event name in methods like addEventListener(), or set an event handler property.

addEventListener("securitypolicyviolation", (event) => { })

onsecuritypolicyviolation = (event) => { }

Event type

A SecurityPolicyViolationEvent. Inherits from Event.

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

Specification
Content Security Policy Level 3> # eventdef-globaleventhandlers-securitypolicyviolation>
HTML> # handler-onsecuritypolicyviolation>

Browser compatibility

	Desktop					Mobile
	Chrome	Edge	Firefox	Opera	Safari	Chrome Android	Firefox for Android	Opera Android	Safari on IOS	Samsung Internet	WebView Android	WebView on iOS
`securitypolicyviolation_event`	41	15	63	28	10	41	63	28	10	4.0	41	10