deploy: 71466f4

no-vary-search.html

@@ -749,7 +749,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">No-Vary-Search</h1>
-   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-08-21">21 August 2024</time></p>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-09-06">6 September 2024</time></p>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version:
@@ -814,8 +814,6 @@ <h2 class="heading settled" data-level="2" id="header-definition"><span class="s
    <p>TODO: probably give some more introductory non-normative text. Look at what other HTTP field defintions do.</p>
    <p>It has the following authoring conformance requirements:</p>
    <ul>
-    <li data-md>
-     <p>The dictionary must only contain entries whose keys are one of <code>key-order</code>, <code>params</code>, <code>except</code>.</p>
     <li data-md>
      <p>If present, the <code>key-order</code> entry’s value must be a <a data-link-type="dfn" href="https://www.rfc-editor.org/rfc/rfc8941.html#name-boolean" id="ref-for-name-boolean">boolean</a>.</p>
     <li data-md>
@@ -825,6 +823,7 @@ <h2 class="heading settled" data-level="2" id="header-definition"><span class="s
     <li data-md>
      <p>The <code>except</code> entry must only be present if the <code>params</code> entry is also present, and the <code>params</code> entry’s value is the boolean value true.</p>
    </ul>
+   <p>The dictionary may contain entries whose keys are not one of <code>key-order</code>, <code>params</code>, and <code>except</code>, but their meaning is not defined by this specification. Implementations of this specification will ignore such entries (but future documents may assign meaning to such entries).</p>
    <p class="note" role="note">As always, the authoring conformance requirements are not binding on implementations. Implementations instead need to implement the processing model given by the <a data-link-type="dfn" href="#obtain-a-url-search-variance" id="ref-for-obtain-a-url-search-variance">obtain a URL search variance</a> algorithm. </p>
    <h2 class="heading settled" data-level="3" id="model"><span class="secno">3. </span><span class="content">Data model</span><a class="self-link" href="#model"></a></h2>
    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="url-search-variance">URL search variance</dfn> is a <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct" id="ref-for-struct">struct</a> whose <a data-link-type="dfn" href="https://infra.spec.whatwg.org/#struct-item" id="ref-for-struct-item">items</a> are the following:</p>
@@ -915,7 +914,10 @@ <h2 class="heading settled" data-level="4" id="parsing"><span class="secno">4. <
      <li data-md>
       <p>Return <var>result</var>.</p>
     </ol>
-    <p class="note" role="note">In general, this algorithm is strict and tends to return the <a data-link-type="dfn" href="#default-url-search-variance" id="ref-for-default-url-search-variance⑧">default URL search variance</a> whenever it sees something it doesn’t recognize. This is because the <a data-link-type="dfn" href="#default-url-search-variance" id="ref-for-default-url-search-variance⑨">default URL search variance</a> behavior will just cause fewer cache hits, which is an acceptable fallback behavior. </p>
+    <div class="note" role="note">
+     <p>In general, this algorithm is strict and tends to return the <a data-link-type="dfn" href="#default-url-search-variance" id="ref-for-default-url-search-variance⑧">default URL search variance</a> whenever it sees something it doesn’t recognize. This is because the <a data-link-type="dfn" href="#default-url-search-variance" id="ref-for-default-url-search-variance⑨">default URL search variance</a> behavior will just cause fewer cache hits, which is an acceptable fallback behavior.</p>
+     <p>However, unrecognized keys at the top level are ignored, to make it easier to extend this specification in the future. To avoid misbehavior with existing client software, such extensions will likely expand, rather than reduce, the set of requests that a cached response can match.</p>
+    </div>
    </div>
    <div class="algorithm" data-algorithm="obtain a URL search variance">
      To <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="obtain-a-url-search-variance">obtain a URL search variance</dfn> given a <a data-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-response" id="ref-for-concept-response">response</a> <var>response</var>: 

prefetch.html

@@ -610,7 +610,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">Prefetch</h1>
-   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-08-21">21 August 2024</time></p>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-09-06">6 September 2024</time></p>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version:

prerendering.html

@@ -773,7 +773,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">Prerendering Revamped</h1>
-   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-08-21">21 August 2024</time></p>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-09-06">6 September 2024</time></p>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version:
@@ -2382,7 +2382,7 @@ <h3 class="no-num no-ref heading settled" id="normative"><span class="content">N
    <dt id="biblio-pointerlock-2">[POINTERLOCK-2]
    <dd>Mustaq Ahmed; Vincent Scheib. <a href="https://w3c.github.io/pointerlock/"><cite>Pointer Lock 2.0</cite></a>. URL: <a href="https://w3c.github.io/pointerlock/">https://w3c.github.io/pointerlock/</a>
    <dt id="biblio-presentation-api">[PRESENTATION-API]
-   <dd>Mark Foltz; Dominik Röttsches. <a href="https://w3c.github.io/presentation-api/"><cite>Presentation API</cite></a>. URL: <a href="https://w3c.github.io/presentation-api/">https://w3c.github.io/presentation-api/</a>
+   <dd>Mark Foltz. <a href="https://w3c.github.io/presentation-api/"><cite>Presentation API</cite></a>. URL: <a href="https://w3c.github.io/presentation-api/">https://w3c.github.io/presentation-api/</a>
    <dt id="biblio-push-api">[PUSH-API]
    <dd>Peter Beverloo; Martin Thomson; Marcos Caceres. <a href="https://w3c.github.io/push-api/"><cite>Push API</cite></a>. URL: <a href="https://w3c.github.io/push-api/">https://w3c.github.io/push-api/</a>
    <dt id="biblio-referrer-policy">[REFERRER-POLICY]

speculation-rules.html

@@ -641,7 +641,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">Speculation Rules</h1>
-   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-08-21">21 August 2024</time></p>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2024-09-06">6 September 2024</time></p>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version: