Bump protocol

Author: mathiasbynens

package-lock.json

@@ -2341,6 +2341,7 @@
             "TextTrack",
             "XHR",
             "Fetch",
+            "Prefetch",
             "EventSource",
             "WebSocket",
             "Manifest",
@@ -2775,6 +2776,17 @@
               "name": "certificateTransparencyCompliance",
               "description": "Whether the request complied with Certificate Transparency policy",
               "$ref": "CertificateTransparencyCompliance"
+            },
+            {
+              "name": "serverSignatureAlgorithm",
+              "description": "The signature algorithm used by the server in the TLS server signature,\nrepresented as a TLS SignatureScheme code point. Omitted if not\napplicable or not known.",
+              "optional": true,
+              "type": "integer"
+            },
+            {
+              "name": "encryptedClientHello",
+              "description": "Whether the connection used Encrypted ClientHello",
+              "type": "boolean"
             }
           ]
         },

pages/_data/1-3.json

@@ -3818,6 +3818,13 @@
                             "items": {
                                 "$ref": "CSSKeyframesRule"
                             }
+                        },
+                        {
+                            "name": "parentLayoutNodeId",
+                            "description": "Id of the first parent element that does not have display: contents.",
+                            "experimental": true,
+                            "optional": true,
+                            "$ref": "DOM.NodeId"
                         }
                     ]
                 },
@@ -10663,6 +10670,7 @@
                         "TextTrack",
                         "XHR",
                         "Fetch",
+                        "Prefetch",
                         "EventSource",
                         "WebSocket",
                         "Manifest",
@@ -11119,6 +11127,17 @@
                             "name": "certificateTransparencyCompliance",
                             "description": "Whether the request complied with Certificate Transparency policy",
                             "$ref": "CertificateTransparencyCompliance"
+                        },
+                        {
+                            "name": "serverSignatureAlgorithm",
+                            "description": "The signature algorithm used by the server in the TLS server signature,\nrepresented as a TLS SignatureScheme code point. Omitted if not\napplicable or not known.",
+                            "optional": true,
+                            "type": "integer"
+                        },
+                        {
+                            "name": "encryptedClientHello",
+                            "description": "Whether the connection used Encrypted ClientHello",
+                            "type": "boolean"
                         }
                     ]
                 },
@@ -15183,6 +15202,7 @@
                         "screen-wake-lock",
                         "serial",
                         "shared-autofill",
+                        "shared-storage",
                         "storage-access-api",
                         "sync-xhr",
                         "trust-token-redemption",

pages/_data/tot.json

@@ -10,7 +10,7 @@ There is no backwards compatibility support guaranteed for the capabilities it i
 
 <h5 browser>Latest <a
    href="https://github.com/ChromeDevTools/devtools-protocol/blob/master/json/browser_protocol.json">browser_protocol.json</a> version updated:</h5>
-<code browser>Date:   2022-06-29 08:28:08 -0700
+<code browser>Date:   2022-07-19 04:49:30 +0000
 </code>
 
 <h5 js>Latest <a