Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Web Share Target #5850

Closed
sorin-davidoi opened this issue Nov 29, 2017 · 3 comments · Fixed by #6278
Closed

Implement Web Share Target #5850

sorin-davidoi opened this issue Nov 29, 2017 · 3 comments · Fixed by #6278
Labels
expertise wanted Extra expertise is needed for implementation

Comments

@sorin-davidoi
Copy link
Contributor

sorin-davidoi commented Nov 29, 2017

The Web Share Target API would allow native apps (e.g. on Android) to share text (and possibly other media) with Mastodon.

Use case:

  • You find a nice quote you want to post on Mastodon
  • You select it and click "Share"
  • You select Mastodon from the share options (it will show up like a native app)
  • Mastodon opens and the text is pasted into the compose field.

This is currently supported in Chrome Canary on Android (source) - but you can feature detect it such that it will automatically become available to everyone as soon as the feature lands in Chrome Stable (and other browsers).

@sorin-davidoi sorin-davidoi added enhancement expertise wanted Extra expertise is needed for implementation labels Nov 29, 2017
@yuntan
Copy link
Contributor

yuntan commented Dec 16, 2017

I've implemented this at yuntan#3. I want to test it with Chrome canary on my Android phone but can't do because someone caches invalid manifest file. I can't estimate how long time to take to settle this incomprehensible behavior...

@sorin-davidoi
Copy link
Contributor Author

@yuntan Do you have any updates? Did they fix the issue?

@yuntan
Copy link
Contributor

yuntan commented Jan 17, 2018

@sorin-davidoi Sorry for inactive. I've been busy for job hunting and cannot respond to this issue until next week. Please refer https://groups.google.com/a/chromium.org/d/msg/blink-dev/_oUskZTzQxg/w4R_YnSXCQAJ about the incomprehensible behavior I experienced. Also note that I've not yet tested @rinsuki 's solution but may be good solution if you want to use /share endpoint instead of /web/statuses/new.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
expertise wanted Extra expertise is needed for implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants