| Issue 620973 | Web Share API | |||||||||||||||||||||||||||||||||||||||||||||
| Starred by 22 users | Project Member Reported by mgiuca@chromium.org, Jun 17 2016 | Back to list | ||||||||||||||||||||||||||||||||||||||||||||
Sign in to add a comment
|
Change description: Web Share is a proposed API for sharing data (text, URLs, images) from the web to an app of the user's choosing. In this first phase, we plan to implement website-to-native-app sharing in Chrome for Android. Changes to API surface: - navigator.share (new API) - navigator.canShare (new API) Links: Public standards discussion: https://discourse.wicg.io/t/web-share-api-for-sharing-content-to-arbitrary-destination/1561/3 Support in other browsers: Internet Explorer: No. Firefox: No. Safari: No.
Comment 1
by
vivekg@chromium.org,
Jun 17 2016
,
Jun 21 2016
**Bulk edit** We are now past M-53 FF. Since you still haven't transitioned to a review state, we are assuming that you are not planning to launch in M-53. As such, we're updating the MStone to M-54. If you still intend to launch in M-53, feel free to change this back, but *please begin your xfnl reviews now*! Thanks for your help with ensuring a smooth process.
,
Jun 22 2016
Since we're planning to launch this behind a flag, the feature freeze doesn't apply and I think it's still viable to land this for M53.
,
Jun 23 2016
FYI type=launch-owp issues aren't for "internal launch tracking" because reasons. (i.e. security, privacy approval etc.). Those reviews happen on type=launch bugs, while type=launch-owp bugs are for external visibility on API progress. I would remove those internal launch tracking labels now but unfortunately don't see how... I think this needs a security review but I don't believe it needs the others so I suggest we don't create a type=launch issue for it, but rather just make sure we've worked with security before launching. Thanks
,
Jun 24 2016
@mgiuca, do you have a component label for this in crbug? It's filed under Blink which is the catchall for incoming triage.
,
Jun 24 2016
#4: I just followed the process at http://www.chromium.org/blink which told me to use this template: https://code.google.com/p/chromium/issues/entry?template=OWP%20Launch%20Tracking It put all of those launch flags on there and I can't get rid of them either (I think it's linked to the Type flag which is Launch-OWP). Seems like this is either intentional or misconfigured. #5: I can't find any component that's relevant to my project. Even if we had a slightly less-general catch-all like "Blink>NewAPIs" or something that would be good.
,
Jul 13 2016
The lack of a component might be the symptom of a problem. What component do you use on the master bug that tracks all the work around Web Share API?
,
Jul 13 2016
It looks like it's issue 595608. And it doesn't even have a component. Can we just add Blink>Web Share component?
,
Jul 14 2016
I was told to add an unofficial component and make it official later. But Monorail won't let me add an unknown component. I CC'd you to an email thread.
,
Jul 20 2016
,
Aug 26 2016
,
Sep 16
,
Nov 18
> we plan to implement website-to-native-app sharing in Chrome for Android. But what about native-app-to-website sharing in Chrome for Android? In context of Web Progressive Apps it would be very useful. PWAs now can be packed to WebAPKs.
,
Nov 20
#13 definitely! We're proposing that as a separate API to keep the discussions separate but we will be starting work on this soon. https://github.com/WICG/web-share-target |
|||||||||||||||||||||||||||||||||||||||||||||
| ► Sign in to add a comment | ||||||||||||||||||||||||||||||||||||||||||||||