Cc: -pkotw...@chromium.org yfried...@chromium.org Owner: pkotw...@chromium.org Summary: Add support for WebShareTarget for WebApks (was: Add support for WebShareTarget experimentation for WebApks)
Peter's going to pick this up since I'll be out for the next 2 weeks
One thing that's absent and which we discussed with you was how to specify multiple share targets? I thought we discussed share_target optionally being an array of dictionaries and you said there was some typical spec way of capturing this (i.e. if only one, can use dictionary, else use array of dict - or something to that effect?)
#4 I was planning to not support that initially and see if there is demand for it.
Allowing multiple share targets introduces significant complexity:
- You need to allow for more than one in the manifest (that part is easy, and we can extend into it later).
- You need to deal with the fact that different platforms will support a different maximum number of share targets, and provide some way for apps to prioritize them and deal with the fact that some may be missing.
- You need to provide additional meta-data such as a name, and possibly icon, for each share target.
- You need to deal with the spoofing concern of apps naming their share targets after some other app. (Whereas if we have only one share target named after the app, we would always show the installed name of the app which the user got to see when they installed it.)
So I would like to just have a single share target for now, with the option of extending later.
Comment 1 by yfried...@chromium.org
, Oct 4 2017Owner: pkotw...@chromium.org
Summary: Add support for WebShareTarget for WebApks (was: Add support for WebShareTarget experimentation for WebApks)