Google has implemented the Web Share API which more info can be found here: https://developers.google.com/web/updates/2016/10/navigator-share The API can be found here: https://github.com/WICG/web-share/blob/master/docs/interface.md The advantages are clear: - Less third party JS loaded on pages to add share buttons - Less tracking - Better UX for users - Less need for 6000 integrations add this site buttons, users use native OS - Simple share implementation for site owners
Component: API: DOM → DOM
Product: Developer Documentation → Core
Coordinated a bit with Google folks on this API. Let's see where it ends up in the DOM triage... maybe something for next year.
> Google has implemented the Web Share API Note that we've only rolled it out in a limited trial which will expire , so we aren't committing to it yet. Thanks for filing the bug. I will keep an eye on this.  https://github.com/jpchase/OriginTrials/
I was going to suggest a extension pollyfill? It doesn't seem something that would fit for test pilot etc. However developers could install and mess about with. Low effort to implement and devs can have a play with it etc. Perhaps even try a different angle to Google implementation etc too for a different view.
Yeah, we can do a polyfill, but it wouldn't be able to share to native apps, nor to a user-customizable set of web apps (since we don't yet have any [registration mechanism](https://github.com/WICG/web-share-target)). The best we'd be able to do is provide a set of popular services (Twitter, Facebook, etc). Still, I think that'd be worth doing.
W3C draft has been published https://wicg.github.io/web-share/
I'm interested in implementing this. If it seems important enough, can somebody mentor me ? Thanks a lot.
@bogas04, maybe after 57 we can find someone to mentor you (as this is low priority right now). However, in the mean time, it would be valuable to make sure the spec has adequate test coverage: https://github.com/w3c/web-platform-tests/tree/master/web-share Reviewing the spec in detail would also be super helpful (and double checking that all assertions are tested). That will make implementation a lot easier, as you'll basically have a complete test suite to code against.
I hope I've covered the spec in sufficient detail in those tests :) But another set of eyes would always be appreciated. I am the author of the Web Share spec and while I can't mentor work on Firefox, I am happy to answer any questions about the spec, test suite and Chrome implementation. Ping me at firstname.lastname@example.org or file issues at https://github.com/WICG/web-share/issues.
(In reply to Matt Giuca from comment #8) > I hope I've covered the spec in sufficient detail in those tests :) From what I saw, they were pretty good. > But another set of eyes would always be appreciated. Agree. Particularly if an adversarial approach is taken (i.e., try to break it and hack the crap out of it). > I am the author of the Web Share spec and while I can't mentor work on > Firefox, I am happy to answer any questions about the spec, test suite and > Chrome implementation. Ping me at email@example.com or file issues at > https://github.com/WICG/web-share/issues.
You need to log in before you can comment on or make changes to this bug.