Document Web Share vs. native share destination capabilities more clearly about web-share HOT 2 CLOSED

If you use Chrome Canary [i.e. the latest nightly build of current Chrome source code], Instagram and Twitter do now show up in the share sheet.

This issue is https://bugs.chromium.org/p/chromium/issues/detail?id=971103

Chrome 75 on Android used ACTION_SEND_MULTIPLE even when a single file was being shared, but apps like Instagram and Twitter only accept ACTION_SEND, not ACTION_SEND_MULTIPLE.

There is no perfect mapping to each platform's sharing model. e.g. with Chrome Canary's Web Share implementation, there is no way to write an Android app that accepts a text field but not a text file. (Both map to ACTION_SEND text/plain.)

I don't think there are plans to make the spec more prescriptive.

from web-share.

Thanks for the quick reply @ewilligers!

I was wondering if the difference had to do with the android.intent.category.BROWSABLE category, I wouldn't have guessed a multiple vs single files flag. Will have to look into the share filtering model(s) further.

Confirmed that this works in Canary, can't wait until it lands in stable.

from web-share.