- From: Matt Giuca <notifications@github.com>
- Date: Fri, 09 Feb 2018 04:25:41 +0000 (UTC)
- To: w3c/WebPlatformWG <WebPlatformWG@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/WebPlatformWG/issues/105@github.com>
Hi, Spinning off from w3c/dap-charter#58, we would like Web Platform WG to consider adopting [Web Share](https://wicg.github.io/web-share/) and [Web Share Target](https://wicg.github.io/web-share-target/) APIs into the charter. The [Web Share](https://wicg.github.io/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](https://wicg.github.io/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). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/WebPlatformWG/issues/105
Received on Friday, 9 February 2018 04:26:04 UTC