On 2013-05-02, at 2:19 AM, Junichi Hashimoto <[email protected]> wrote: > These issues are solved if WebActivity has an option to set the receiver > when it is invoked and has the sender information when it is passed to > the receiver. As the identity for the option and the information > manifest URL seems suitable. I don't think to make another API for the > above purpose. To keep existing codes working the functionality should > be provided as an option.
Isn't this also how Android works? I think there are three things that can happen on Android: 1) If you start an activity and there is only one application registered to handle that activity, that app is chosen and started without user interaction. 2) If you start an activity and there are multiple applications registered to handle that activity, the user is given a choice to choose the application and also to mark the application as default. If the default is set then Android will not ask you in the future. 3) If you start an activity and you send it to a specific application (by its bundle id) then that the activity is passed to that app without user interaction. On Firefox OS we have 1 and 2 now and AFAIK 3 is missing. Is that the option that you are interested in? I think that could make sense. Right now MozActivityOptions only has name and data attributes but we could extend that with a preferred app. S. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
