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
{{ message }}
This repository was archived by the owner on Nov 15, 2021. It is now read-only.
The Web Share API has been in WICG for a long time now, and is fairly mature. While it only has one implementation (Chrome), it had a lot of interest from other vendors, and we would like to move it onto a standards track. This adds a single new method, navigator.share, which allows a web page to trigger a share event to an arbitrary destination of the user's choice. It is up to the implementation what choices are available; typically it would go into the host OS's share system.
The companion API, Web Share Target, Web Share Target, allows sites to register to receive shared data, from Web Share but also from the host OS's share system. This API is not as far along, with a number of outstanding issues on the spec draft, and while there are prototype implementations in Chrome, nothing has been released. There is more controversy over the syntax and nature of the API, and it's generally a bit more complex. Eventually, it makes sense for WST to become part of the Manifest API, and the spec has been written with that in mind.
Therefore, I think both of these APIs are a good fit for the Web Platform WG (which also hosts the Manifest API).
The text was updated successfully, but these errors were encountered:
Mozilla position discussion. There is support from many people within Mozilla, but note the objection from @tantek, primarily that Web Share would be harmful without Web Share Target (partly why I'm asking to charter both of these at the same time).
Apple bug. No intent to commit but they have said it's "interesting" and are tracking it.
Web Share Target
Mozilla position: No explicit position, but note the above objection that would be resolved by Web Share Target.
Hi,
Spinning off from w3c/das-charter#58, we would like Web Platform WG to consider adopting Web Share and Web Share Target APIs into the charter.
The Web Share API has been in WICG for a long time now, and is fairly mature. While it only has one implementation (Chrome), it had a lot of interest from other vendors, and we would like to move it onto a standards track. This adds a single new method,
navigator.share
, which allows a web page to trigger a share event to an arbitrary destination of the user's choice. It is up to the implementation what choices are available; typically it would go into the host OS's share system.The companion API, Web Share Target, Web Share Target, allows sites to register to receive shared data, from Web Share but also from the host OS's share system. This API is not as far along, with a number of outstanding issues on the spec draft, and while there are prototype implementations in Chrome, nothing has been released. There is more controversy over the syntax and nature of the API, and it's generally a bit more complex. Eventually, it makes sense for WST to become part of the Manifest API, and the spec has been written with that in mind.
Therefore, I think both of these APIs are a good fit for the Web Platform WG (which also hosts the Manifest API).
The text was updated successfully, but these errors were encountered: