From 0eaf73c9897aa608bd59060e6f705a967b2551ed Mon Sep 17 00:00:00 2001 From: Marcos Caceres Date: Tue, 28 Feb 2023 18:05:57 -0800 Subject: [PATCH] chore: tidy --- index.html | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/index.html b/index.html index 0201f17..9d0c450 100644 --- a/index.html +++ b/index.html @@ -494,8 +494,8 @@

positive results when used with objects that contain members not defined in the `ShareData` dictionary. Because of how WebIDL works, browsers drop unknown members from the input object and - will return `true` when testing the remaining members. This behavior is - not future-compatible. + will return `true` when testing the remaining members. This + behavior is not future-compatible.

To ensure reliable testing of shareability, developers can @@ -505,13 +505,13 @@

members individually.

- Although this doesn't affect any implementations today, - the Working Group will work towards addressing this issue in a future + Although this doesn't affect any implementations today, the + Working Group will work towards addressing this issue in a future revision of the specification - especially if we make any - amendments to the `ShareData` dictionary. - To contribute ideas for how to address this issue, see - issue #108 - on GitHub. + amendments to the `ShareData` dictionary. To contribute ideas for + how to address this issue, see issue #108 on + GitHub.

@@ -717,8 +717,8 @@

to use=] the API by default.

- It is OPTIONAL for user agents to support - [[[PERMISSIONS-POLICY]]]'s `Permissions-Policy` HTTP header. + It is OPTIONAL for user agents to support [[[PERMISSIONS-POLICY]]]'s + `Permissions-Policy` HTTP header.

Developers can use the means afforded by the [[[permissions-policy]]] @@ -729,19 +729,19 @@

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 issues 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. + are interoperability issues 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.

- When the `Permissions-Policy` HTTP header is more widely supported, - the Working Group expects to revise this specification - to require support for the header. + When the `Permissions-Policy` HTTP header is more widely supported, + the Working Group expects to revise this specification to require + support for the header.