CFC to publish Web Share as a W3C Recommendation

[marcoscaceres]

This is a call for consensus (CFC) to publish the Web Share API specification as a W3C Recommendation.

During the Proposed Recommendation phase, we received a formal objection from Mozilla [1], which resulted in some editorial changes (detailed below). We have been coordinating with Mozilla to address their concerns and we believe that all issues raised during the Proposed Recommendation phase have been resolved. We are now just waiting for confirmation that the issues have been addressed to their satisfaction.

In the meantime, we feel confident in initiating this CFC, which ends at midnight 12 April, 2023.

Please indicate your support for publishing the specification as a W3C Recommendation in the Github issue linked below using either the 👍 or 👎 (formal objection) reaction buttons of the issue.

If you have a formal objection (i.e., you indicate 👎) to its publication, we kindly ask that you raise it before 12 April, 2023.
You can view the latest Proposed Recommendation here:
https://www.w3.org/TR/web-share/

The abstract reads: "This specification defines an API for sharing text, links and other content to an arbitrary destination of the user's choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts.”

As stated in the last CFC, the API has received wide review and is implemented in an interoperable manner across all major browser engines and across a range of platforms. It also has significant usage across the Web.

Details about how we handled the formal objection

During the Proposed Recommendation phase, we received a formal objection from Mozilla. We have been working with Mozilla to address their concerns and make some editorial changes, which are detailed below. We believe that all issues raised during the Proposed Recommendation phase have been resolved to their satisfaction.

In addition to addressing the formal objection, a few editorial issues and questions were raised during the Proposed Recommendation phase, all of which were resolved:

• What's the scope of "abort these steps"? #266 (editorial)
• Suggesting preview for security should mention accessibility #264 (editorial)
• Base isn't needed in main branch of algorithm #259 (invalid)
• Support additional media types? #258 (question)

We appreciate the feedback from all participants in the Web Share API specification process, and we are committed to ensuring that the specification meets the needs of the Web community.

[marcoscaceres]

Just a heads up that we've updated the spec to make Permissions-Policy HTTP header optional:
#275

This is because neither WebKit or Gecko supports the header right now. When that situation changes, we will update the spec.

[marcoscaceres]

CFC passed with no objections.

[marcoscaceres]

Document will be published soon. We are just waiting to hear from one of the reviewers.