Search results

Broken links in Content Security Policy Level 3

Status: Open.

#789 In w3c/webappsec-csp;

· dontcallmedom-bot opened on Nov 3, 2025

Incorrect assertion in Obtain the deprecated serialization of violation

Status: Open.

#788 In w3c/webappsec-csp;

· Lubrsi opened on Oct 30, 2025

Incorrect assertion in form-action Pre-Navigation Check

Status: Open.

#782 In w3c/webappsec-csp;

· Lubrsi opened on Jul 28, 2025

<code>report-multiple-violations-{01,02}</code> don't conform with the spec

Status: Open.

#781 In w3c/webappsec-csp;

· TimvdLippe opened on Jul 11, 2025

CSP report referrer should adhere to referrer policy

Status: Open.

#775 In w3c/webappsec-csp;

· imolorhe-stripe opened on Jul 7, 2025

setting cssText rather than style

Status: Open.

#774 In w3c/webappsec-csp;

· johanneswilm opened on Jul 1, 2025

Making CSP more usable for organizations at scale

Status: Open.

#736 In w3c/webappsec-csp;

· swijckmans opened on Jun 18, 2025

Implementation differences with "Strip URL for use in reports"

Status: Open.

#735 In w3c/webappsec-csp;

· evilpie opened on Jun 13, 2025

Add Back The <code>prefetch-src</code> Directive to The CSP Header

Status: Open.

#733 In w3c/webappsec-csp;

· zphrs opened on Jun 6, 2025

report-to directive to support multiple endpoints

Status: Open.

#785 In w3c/webappsec-csp;

· armenzg opened on May 23, 2025

Strict-Dynamic CSP doesn't prevent execution of parser inserted scripts via document.createRange().createContextualFragment

Status: Open.

#708 In w3c/webappsec-csp;

· andreituicu opened on Feb 26, 2025

"source file" lacks a real defintion

clarificationThe standard is unclear or ambiguousThe standard is unclear or ambiguous

interopImplementations are not interoperable with each otherImplementations are not interoperable with each other

Status: Open.

#707 In w3c/webappsec-csp;

· evilpie opened on Feb 14, 2025