CR Request for Web Share API

[siusin]

Note: the CfC ends on 29 Jul

Document title, URLs, estimated publication date

Web Share API https://www.w3.org/TR/web-share/ 02 August 2022

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.

Status

This is a work in progress. Wide review and feedback welcome.

This document was published by the Web Applications Working Group as a Candidate Recommendation Snapshot using the Recommendation track. Publication as a Candidate Recommendation does not imply endorsement by W3C and its Members. A Candidate Recommendation Snapshot has received wide review, is intended to gather implementation experience, and has commitments from Working Group members to royalty-free licensing for implementations.

The specification identifies one feature at risk:

• Permissions policy 'self' is at risk #169 - due to web compatibility issues.

This Candidate Recommendation is not expected to advance to Proposed Recommendation any earlier than 30 August 2022.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. This document is governed by the 2 November 2021 W3C Process Document.

Link to group's decision to request transition

The CfC ends on 29 Jul

Changes

None.

Requirements satisfied

None.

Dependencies met (or not)

Web Share API has a few normative references on Permissions Policy, which hasn't got enough implementation commitments. This has been identified as an at-risk feature in the SoTD.

Wide Review

• APA
• TAG
• I18n (1 issue reported, but closed because of nothing actionable)
• Privacy (2 issues reported, already addressed)
• Security (2 issues reported, already addressed)

Issues addressed

There are two open issues in the repo:

• #169 identifies an at-risk feature;
• #109 remains open for discussion about future improvement;

Formal Objections

None.

Implementation

The spec is implemented in an interoperable manner across all major browser engines across a range of platforms and has wide usage across the Web.

Patent disclosures

https://www.w3.org/groups/wg/webapps/ipr

[plehegar]

Should be https://github.com/w3c/web-share/issues/169

[swickr]

The Review Dashboard says there are 8 'needs-resolution' issues remaining open. Please close the loop with I18N, Security, PING, and TAG to confirm the status of those issues.

During CR if the WG decides to drop the At Risk feature, please obtain feedback from privacy reviewers.

[plehegar]

cc @w3c/horizontal-admin since this affects several horizontal groups.

[marcoscaceres]

Pinged all the wide-review groups/folks requesting they take a look at how each issue was addressed. Quite a few have acknowledged that their concerns have been addressed but they just forgot to remove the label.

[aphillips]

Quite a few have acknowledged that their concerns have been addressed but they just forgot to remove the label.

At least with regard to I18N, we don't remove the labels (and neither should you): you close your issue and we close our mirroring issue in i18n-activity. It is the closure of the mirroring issue that gets your "open" count down to zero: these are the items that appear in the Review Dashboard.

[pes10k]

Thank you for the nudge @marcoscaceres . The PING-member who filed the original privacy issues is no longer involved in PING. We'll review and discuss on our next call (Thursday, Aug 4) and then close out issues or follow up accordingly.

[r12a]

I have sent an agenda+ to review the one outstanding i18n issue at our next telecon on Thursday.

[marcoscaceres]

Yep, no touching the labels 😇 I had forgotten.

[aphillips]

Just to confirm: I18N is satisfied by the fix to our reported issue and has no remaining issues against this spec. Good luck with your transition!

[marcoscaceres]

@pes10k, how did things go on the call? I added links in the various issues outlining where/how things were addressed.

[pes10k]

Yep, i've closed out the privacy tracking issues. You should be all good to go

[marcoscaceres]

Thanks @pes10k. Appreciate it! 🙏

[marcoscaceres]

Pinged the TAG again. What's a reasonable amount of time to wait on them? Their issues were addressed well over a year ago.

@plehegar or @samuelweiler, could you please close: https://github.com/w3c/security-review/issues/122 https://github.com/w3c/security-review/issues/114

[marcoscaceres]

Tag issues are now closed ✅

[marcoscaceres]

@siusin, should we push to publish before the moratorium? Let me know if I can be of any help generating the snapshot or if there are pub rules issues.

[siusin]

@marcoscaceres sure, will do!

[siusin]

@swickr @plehegar please let us know if you have any concerns that the group will move forward and publish the CR, before next Tuesday.

[swickr]

Transition approved.

https://github.com/w3c/security-review/issues/122 isn't yet closed but that is the tracking issue for https://github.com/w3c/web-share/issues/223 wherein the commenter said they were satisfied, so I conclude that the security review is completely.

As of this date I see a lot of red in the WPT report. We'll want to see more explanation of status of implementations before Proposed Rec.

[marcoscaceres]

@swickr, thanks for approving.

I'll add details to the implementation report. The short answer is: for Chrome, it's only supported on Android; and for Firefox, only on Windows.

However, both Edge and Safari will have full passing test suite in a few weeks. That should allow us to go to PR 🤞.

[ewilligers]

For Chrome, it is supported on Android, ChromeOS and Windows.

[marcoscaceres]

oh, fantastic! thanks for the update @ewilligers.

[siusin]

Thank you all!

Web Share API is a W3C Candidate Recommendation Snapshot: https://www.w3.org/TR/2022/CR-web-share-20220823/