CFC: Publish Web Share API as a Candidate Recommendation

Dear Working Group Participants, 

This is a call for consensus (CFC) to publish the "Web Share API" specification as a Candidate Recommendation (CR). The CFC ends at midnight on Friday the 29th of July, 2022. We expect the CR phase to run until after TPAC (~September/October, 2022) to allow implementations to iron out some last remaining interoperability issues. 

From the abstract: "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."

You can view the latest Working Draft here: https://www.w3.org/TR/web-share/

The specification has received wide review and is interoperable across all major browser engines and is available on a range of platforms. Further, it has seen significant uptake by web developers and is now a feature of popular websites, such as YouTube.

However, the specification identifies one feature "at risk":

 • Permissions policy 'self' is at risk (see [at-risk] link below) - due to web compatibility issues.

Please indicate your support for publishing the specification as a W3C Candidate Recommendation in the Github issue linked below using either the 👍 or 👎 (formal objection) reaction buttons of this issue. If you have a formal objection (i.e., you indicate "👎") to its publication, we kindly ask that you provide a detailed rationale for the objection, either here or in the Github issue below: 

https://github.com/w3c/web-share/issues/246

Kind regards,
Marcos and Leonie (Chairs), and Xiaoqian (Team Contact)

[at-risk] https://github.com/w3c/web-share/issues/169

Received on Tuesday, 12 July 2022 05:22:09 UTC