diff --git a/index.html b/index.html index e3d5777..9d1ae22 100644 --- a/index.html +++ b/index.html @@ -49,9 +49,9 @@ * - ::before styled for CSS-generated issue/example/figure numbers: * -> Documents wishing to use this only need to add * figcaption::before, - * .caption::before { content: "Figure " counter(figure); } - * .example::before { content: "Example " counter(example); } - * .issue::before { content: "Issue " counter(issue); } + * .caption::before { content: "Figure " counter(figure) " "; } + * .example::before { content: "Example " counter(example) " "; } + * .issue::before { content: "Issue " counter(issue) " "; } * * Header Stuff (ignore, just don't conflict with these classes) * - .head for the header @@ -457,7 +457,7 @@ font-style: normal; } dt dfn code, code.idl { - font-size: inherit; + font-size: normal; } dfn var { font-style: normal; @@ -646,7 +646,7 @@ padding-right: 1em; text-transform: uppercase; } - /* Add .issue::before { content: "Issue " counter(issue); } for autogen numbers, + /* Add .issue::before { content: "Issue " counter(issue) " "; } for autogen numbers, or use class="marker" to mark up the issue number in source. */ /** Example *******************************************************************/ @@ -664,7 +664,7 @@ min-width: 7.5em; display: block; } - /* Add .example::before { content: "Example " counter(example); } for autogen numbers, + /* Add .example::before { content: "Example " counter(example) " "; } for autogen numbers, or use class="marker" to mark up the example number in source. */ /** Non-normative Note ********************************************************/ @@ -1421,7 +1421,7 @@

Content Security Policy Level 3

-

Editor’s Draft,

+

Editor’s Draft,

This version: @@ -2379,7 +2379,6 @@

§4.2.5 Should navigation response to navigation request of type from source in target be blocked by Content Security Policy? is called during the process a navigate response algorithm to apply directive’s navigation checks.

-

Upstream this to HTML. <https://github.com/whatwg/html/issues/1230>

W3C’s HTML is not based on Fetch, and does not have a process a navigate response algorithm into which to hook. <https://github.com/w3c/html/issues/548>

@@ -2592,31 +2591,31 @@

5. report may be generated and sent out to a reporting endpoint associated with the policy.

5.1. Violation DOM Events

-
[Constructor(DOMString type, optional SecurityPolicyViolationEventInit eventInitDict)]
+
[Constructor(DOMString type, optional SecurityPolicyViolationEventInit eventInitDict)]
 interface SecurityPolicyViolationEvent : Event {
-    readonly    attribute DOMString      documentURI;
-    readonly    attribute DOMString      referrer;
-    readonly    attribute DOMString      blockedURI;
-    readonly    attribute DOMString      violatedDirective;
-    readonly    attribute DOMString      effectiveDirective;
-    readonly    attribute DOMString      originalPolicy;
-    readonly    attribute DOMString      sourceFile;
-    readonly    attribute unsigned short statusCode;
-    readonly    attribute long           lineNumber;
-    readonly    attribute long           columnNumber;
+    readonly    attribute DOMString      documentURI;
+    readonly    attribute DOMString      referrer;
+    readonly    attribute DOMString      blockedURI;
+    readonly    attribute DOMString      violatedDirective;
+    readonly    attribute DOMString      effectiveDirective;
+    readonly    attribute DOMString      originalPolicy;
+    readonly    attribute DOMString      sourceFile;
+    readonly    attribute unsigned short statusCode;
+    readonly    attribute long           lineNumber;
+    readonly    attribute long           columnNumber;
 };
 
-dictionary SecurityPolicyViolationEventInit : EventInit {
-    DOMString      documentURI;
-    DOMString      referrer;
-    DOMString      blockedURI;
-    DOMString      violatedDirective;
-    DOMString      effectiveDirective;
-    DOMString      originalPolicy;
-    DOMString      sourceFile;
-    unsigned short statusCode;
-    long           lineNumber;
-    long           columnNumber;
+dictionary SecurityPolicyViolationEventInit : EventInit {
+    DOMString      documentURI;
+    DOMString      referrer;
+    DOMString      blockedURI;
+    DOMString      violatedDirective;
+    DOMString      effectiveDirective;
+    DOMString      originalPolicy;
+    DOMString      sourceFile;
+    unsigned short statusCode;
+    long           lineNumber;
+    long           columnNumber;
 };
 

     
5.2.  Obtain the deprecated serialization of violation 

@@ -2682,47 +2681,47 @@ 

-        
documentURI

+        
documentURI

        

         
violation’s url

        

-        
referrer

+        
referrer

        

         
violation’s referrer

        

-        
blockedURI

+        
blockedURI

        

         
violation’s resource

        

-        
effectiveDirective

+        
effectiveDirective

        

         
violation’s effective directive

        

-        
violatedDirective

+        
violatedDirective

        

         
violation’s effective directive

        

-        
originalPolicy

+        
originalPolicy

        

         
violation’s policy

        

-        
sourceFile

+        
sourceFile

        

         
violation’s source file

        

-        
statusCode

+        
statusCode

        

         
violation’s status

        

-        
lineNumber

+        
lineNumber

        

         
violation’s line number

        

-        
columnNumber

+        
columnNumber

        

         
violation’s column number

-

Note: Both effectiveDirective and violatedDirective are the same value. +

Note: Both effectiveDirective and violatedDirective are the same value. This is intentional to maintain backwards compatibility.

  • If violation’s policy’s directive @@ -4796,8 +4795,20 @@

    ancestor-source-list, in §6.3.2
  • base64-value, in §2.2.1
  • base-uri, in §6.2.1 +
  • + blockedURI +
  • child-src, in §6.1.1
  • column number, in §2.3 +
  • + columnNumber +
  • connect-src, in §6.1.2
  • Content-Security-Policy, in §3.1
  • Content Security Policy, in §1 @@ -4810,12 +4821,24 @@

    directive-value, in §2.2
  • disown-opener, in §6.2.4
  • disposition, in §2.1 +
  • + documentURI +
  • effective directive +
  • + effectiveDirective +
  • embedding document, in §4.2
  • enforced, in §4.2
  • EnsureCSPDoesNotBlockStringCompilation(callerRealm, calleeRealm), in §4.3 @@ -4835,6 +4858,12 @@

    inline check, in §2.2
  • keyword-source, in §2.2.1
  • line number, in §2.3 +
  • + lineNumber +
  • manifest-src, in §6.1.7
  • media-src, in §6.1.8
  • media-type, in §6.2.2 @@ -4845,6 +4874,12 @@

    nonce-source, in §2.2.1
  • 'none', in §2.2.1
  • object-src, in §6.1.9 +
  • + originalPolicy +
  • parse a serialized CSP, in §2.1
  • path-part, in §2.2.1
  • plugin-types, in §6.2.2 @@ -4859,7 +4894,13 @@

    post-request check, in §2.2
  • pre-navigation check, in §2.2
  • pre-request check, in §2.2 -
  • referrer, in §2.3 +
  • + referrer +
  • report-to, in §6.4.2
  • report-uri, in §6.4.1
  • resource, in §2.3 @@ -4869,6 +4910,9 @@

    scheme-source, in §2.2.1
  • script-src, in §6.1.10
  • SecurityPolicyViolationEvent, in §5.1 +
  • SecurityPolicyViolationEventInit, in §5.1 +
  • SecurityPolicyViolationEvent(type), in §5.1 +
  • SecurityPolicyViolationEvent(type, eventInitDict), in §5.1
  • 'self', in §2.2.1
  • serialized CSP, in §2.1
  • serialized directive, in §2.2 @@ -4880,8 +4924,20 @@

    source-expression, in §2.2.1
  • source expression, in §2.2.1
  • source file, in §2.3 +
  • + sourceFile +
  • source lists, in §2.2.1
  • status, in §2.3 +
  • + statusCode +
  • 'strict-dynamic', in §2.2.1
  • style-src, in §6.1.11
  • 'unsafe-eval', in §2.2.1 @@ -4889,6 +4945,12 @@

    'unsafe-inline', in §2.2.1
  • url, in §2.3
  • value, in §2.2 +
  • + violatedDirective +
  • violation, in §2.3
  • violation report, in §5
  • worker-src, in §6.1.12 @@ -5094,24 +5156,6 @@

  • Worker -
  • - [CSP1] defines the following terms: -
  • [css-cascade-4] defines the following terms:

    • This hook is missing from W3C’s HTML. <https://github.com/w3c/html/issues/547> ↵
    -
    Upstream this to HTML. <https://github.com/whatwg/html/issues/1230> ↵
    W3C’s HTML is not based on Fetch, and does not have a process a navigate response algorithm into which to hook. <https://github.com/w3c/html/issues/548> ↵
    This needs to be better explained. ↵
    @@ -6232,6 +6273,83 @@

    (2) + + + + + + + + + + +