From bee23445a3c1aa204d7a48fd31850bc08633ba8b Mon Sep 17 00:00:00 2001
From: Marcos Caceres <marcos@marcosc.com>
Date: Mon, 12 Dec 2022 11:41:25 +1100
Subject: [PATCH 1/2] Editorial: address Proposed Rec feedback

---
 index.html | 26 +++++++++++++++++---------
 1 file changed, 17 insertions(+), 9 deletions(-)

diff --git a/index.html b/index.html
index ef68ca4..5e7389f 100644
--- a/index.html
+++ b/index.html
@@ -190,7 +190,7 @@ <h3>
           text: "This is a text to share",
           someFutureThing: "some future thing",
         };
-        
+
         // Things that are not supported...
         const unsupported = Object.entries(data).filter(([key, value]) =&gt; {
           return !navigator.canShare({ [key]: value });
@@ -200,8 +200,8 @@ <h3>
         Enabling the API in third-party contexts
       </h3>
       <p data-cite="permissions-policy">
-        The [=default allowlist=] of `'self'` makes Web Share API available by
-        default only in first-party contexts.
+        The [=default allowlist=] of [=default allowlist/'self'=] makes Web
+        Share API available by default only in first-party contexts.
       </p>
       <p>
         Third-party can be allowed to use this API via an [^iframe^]'s
@@ -680,20 +680,28 @@ <h2>
       <p>
         This specification defines a policy-controlled permission identified by
         the string <code><dfn class="permission">"web-share"</dfn></code>. Its
-        <a>default allowlist</a> is [=default allowlist/'self'=].
+        [=default allowlist=] is [=default allowlist/'self'=], which means
+        third-party contexts are not [=allowed to use=] the API by default.
       </p>
       <p>
         Developers can use the means afforded by the [[[permissions-policy]]]
         specification to control if and when a third-party context is [=allowed
         to use=] this API.
       </p>
-      <div class="note">
+      <aside class="note" title="Permissions Policy Implementation Status">
         <p>
-          A <a>document</a>'s permission policy determines whether a
-          {{Navigator/share()}} call immediately rejects with a
-          {{"NotAllowedError"}} {{DOMException}}.
+          Although user agents are unified in preventing the Web Share API from
+          being used in third-party context, at the time of publication there
+          are interoperability with relying on the [[[Permissions-Policy]]] to
+          enable the API in third-party contexts. In particular, although
+          the[^iframe/allow^] attribute is widely supported, the updated syntax
+          for the [^iframe/allow^] attribute is not. Similarly, the
+          `Permissions-Policy:` HTTP header is not yet widely supported.
+          Developers are advised to check the implementation status of the
+          [[[Permissions-Policy]]] specification before relying on it to enable
+          the Web Share API in third-party contexts.
         </p>
-      </div>
+      </aside>
     </section>
     <section class="informative">
       <h2>

From ed052537bdf962db72b6d7fd778df42090f96341 Mon Sep 17 00:00:00 2001
From: Marcos Caceres <marcos@marcosc.com>
Date: Mon, 12 Dec 2022 11:53:28 +1100
Subject: [PATCH 2/2] Add test about updatable-rec

---
 index.html | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/index.html b/index.html
index 5e7389f..b85cf5a 100644
--- a/index.html
+++ b/index.html
@@ -77,6 +77,11 @@ <h3>
           more available across all OSs over time, and is already widely
           available on popular OSs across a range of devices.
         </p>
+        <p>
+          <!-- TODO: Remove me when this goes to REC, otherwise it will show up twice! -->
+           Future updates to this Recommendation may incorporate [new
+          features](https://www.w3.org/2021/Process-20211102/#allow-new-features).
+        </p>
       </section>
     </section>
     <section class="informative">