@@ -494,8 +494,8 @@ <h3>
494494 positive results when used with objects that contain members not
495495 defined in the `ShareData` dictionary. Because of how WebIDL
496496 works, browsers drop unknown members from the input object and
497- will return `true` when testing the remaining members. This behavior is
498- not future-compatible.
497+ will return `true` when testing the remaining members. This
498+behavior is not future-compatible.
499499</p>
500500<p>
501501 To ensure reliable testing of shareability, developers can
@@ -505,13 +505,13 @@ <h3>
505505 members individually.
506506</p>
507507<p>
508- Although this doesn't affect any implementations today,
509-the Working Group will work towards addressing this issue in a future
508+ Although this doesn't affect any implementations today, the
509+ Working Group will work towards addressing this issue in a future
510510 revision of the specification - especially if we make any
511- amendments to the `ShareData` dictionary.
512-To contribute ideas for how to address this issue, see
513-<a href="https://github.com/w3c/web-share/issues/108">issue #108</a>
514-on GitHub.
511+ amendments to the `ShareData` dictionary. To contribute ideas for
512+ how to address this issue, see <a href=
513+ "https://github.com/w3c/web-share/issues/108">issue #108</a> on
514+ GitHub.
515515</p>
516516</aside>
517517</section>
717717 to use=] the API by default.
718718</p>
719719<p>
720- It is OPTIONAL for user agents to support
721-[[[PERMISSIONS-POLICY]]]'s `Permissions-Policy` HTTP header.
720+ It is OPTIONAL for user agents to support [[[PERMISSIONS-POLICY]]]'s
721+ `Permissions-Policy` HTTP header.
722722</p>
723723<p>
724724 Developers can use the means afforded by the [[[permissions-policy]]]
@@ -729,19 +729,19 @@ <h2>
729729<p>
730730 Although user agents are unified in preventing the Web Share API from
731731 being used in third-party context, at the time of publication there
732- are interoperability issues with relying on the [[[Permissions-Policy]]] to
733- enable the API in third-party contexts. In particular, although
734- the[^iframe/allow^] attribute is widely supported, the updated syntax
735- for the [^iframe/allow^] attribute is not. Similarly, the
736- `Permissions-Policy:` HTTP header is not yet widely supported.
737- Developers are advised to check the implementation status of the
738- [[[Permissions-Policy]]] specification before relying on it to enable
739- the Web Share API in third-party contexts.
732+ are interoperability issues with relying on the
733+[[[Permissions-Policy]]] to enable the API in third-party contexts.
734+In particular, although the[^iframe/allow^] attribute is widely
735+supported, the updated syntax for the [^iframe/allow^] attribute is
736+not. Similarly, the `Permissions-Policy:` HTTP header is not yet
737+widely supported. Developers are advised to check the implementation
738+status of the [[[Permissions-Policy]]] specification before relying
739+on it to enable the Web Share API in third-party contexts.
740740</p>
741741<p>
742- When the `Permissions-Policy` HTTP header is more widely supported,
743- the Working Group expects to revise this specification
744-to require support for the header.
742+ When the `Permissions-Policy` HTTP header is more widely supported,
743+ the Working Group expects to revise this specification to require
744+ support for the header.
745745</p>
746746</aside>
747747</section>
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。