You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The API has received wide review and is implemented in an interoperable manner across all major browser engines across a range of platforms and has wide usage across the Web.
However, the specification identifies one feature at risk:
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 an formal objection (i.e., you indicate 👎) to its publication, we kindly ask that you raise it before 29th of July, 2022: #246
The text was updated successfully, but these errors were encountered:
This is a call for consensus (CFC) to publish the Web Share API specification as a Candidate Recommendation.
The CFC ends at midnight on Friday the 29th of July, 2022.
You can view the latest working draft here (synced with Editor's draft):
https://www.w3.org/TR/web-share/
The abstract reads:
The API has received wide review and is implemented in an interoperable manner across all major browser engines across a range of platforms and has wide usage across the Web.
However, the specification identifies one feature at risk:
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 an formal objection (i.e., you indicate 👎) to its publication, we kindly ask that you raise it before 29th of July, 2022: #246
The text was updated successfully, but these errors were encountered: