6.7.2.4 Does request match source list?.6.7.2.2 Does resource hint request violate policy?.6.7.1.2 Script directives post-request check.
6.1.14.2 style-src-elem Post-request Check.6.1.14.1 style-src-elem Pre-request Check.6.1.11.2 script-src-elem Post-request check.6.1.11.1 script-src-elem Pre-request check.6.1.10.2 script-src Post-request check.6.1.7.2 manifest-src Post-request check.6.1.7.1 manifest-src Pre-request check.6.1.3.2 default-src Post-request check.6.1.2.2 connect-src Post-request check.5.3 Obtain the deprecated serialization of violation.5.2 Obtain the blockedURI of a violation’s resource.4.5.1 EnsureCSPDoesNotBlockWasmByteCompilation realm.4.4.1 EnsureCSPDoesNotBlockStringCompilation( realm, source).4.3.1 Should RTC connections be blocked for global?.4.2.6 Run CSP initialization for a global object.4.2.5 Should navigation response to navigation request of type in target be blocked by Content Security Policy?.4.2.4 Should navigation request of type be blocked.4.2.3 Should element’s inline type behavior be blocked by Content Security Policy?.4.2.2 Retrieve the CSP list of an object.4.2.1 Run CSP initialization for a Document.4.1.3 Should response to request be blocked by Content Security Policy?.4.1.2 Should request be blocked by Content Security Policy?.4.1.1 Report Content Security Policy violations for request.3.2 The Content-Security-Policy-Report-Only HTTP Response Header Field.3.1 The Content-Security-Policy HTTP Response Header Field.2.4.2 Create a violation object for request, and policy.2.4.1 Create a violation object for global, policy, and directive.2.2.3 Parse response’s Content Security Policies.It means that the WG believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the WG to drop the feature if necessary when transitioning to the Proposed Rec stage, without having to publish a new Candidate Rec without the feature first. “At-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. The § 6.7.3.1 Is element nonceable? algorithm.The following features are at-risk, and may be dropped during the CR period:
This document is governed by the 2 November 2021 W3C Process Document. That page also includes instructions for disclosing a patent.Īn individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group This document was produced by a group operating under This document was produced by the Web Application Security Working Group. Obsoleted by other documents at any time. This is a draft document and may be updated, replaced or Publication as a Working Draft does not imply endorsement by W3C and its Members. Please put the text “CSP3” in the subject, Is preferred for discussion of this specification. The ( archived) public mailing list (see instructions) This document is intended to become a W3C Recommendation. This document was published by the Web Application Security Working Group as a Working Draft using the Recommendation This section describes the status of this document at the time ofĬurrent W3C publications and the latest revision of this technical reportĬan be found in the W3C technical reports
0 kommentar(er)
