Intent to Migrate: Web Share API
Hi Folks working on this... with the Web Apps WG now up and running, we are ready to adopt this specification into the WG for formal standardization along the w3c rec track. π
Before doing so, I could use a bit of help just filling out the template below... I've got things started already, but those with knowledge of the spec please jump in.
Working group decision to adopt
In W3C WebApps Charter
Proposal
https://github.com/WICG/web-share/
Adopt level/version 1 and 2?
Summary
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.
Motivation and Use Cases
Described in the explainer.
Compatibility Risk
Please characterize how much we might regret standardizing this new feature were we to change or remove it in the future. If you donβt have a github repository, include in this email links to relevant discussions, or documentation about support for the feature on the Web.
As the feature is shipping in two browsers, there is risk with making too many changes to v1 of this API. However, it would be good to perform conformance/interop testing, and address any issues during the next phase of the standardization process.
Ongoing technical constraints
Discussion of options on various operating systems:
https://github.com/WICG/web-share/blob/master/docs/native.md
Not supported as a native feature across all operating systems. It is foreseeable that browsers could "share" across web apps, via the Share Target API.
Link to implementation experience and demos
Implemented in Chrome (since 61) and Safari (since 66).
Was also trialed/used on twitter.com. (still used there?)
Data
What data do you have available that indicates that this enhancement will affect many users of the Web. Quantify the fraction of websites that are currently using something similar to this feature. Or, if a new feature, characterize the reason that you expect this to be far reaching.
Security and Privacy
Outline the security and privacy implications of your proposal for end-users. Otherwise, indicate if there are none.
Accessibility
Outline the implications of your proposal relative to access by everyone regardless of disability. Otherwise, indicate if there are none.
Internationalization
See issue #6