On 17/07/15 22:06, Brian Nicholson wrote: > It's also worth mentioning that there's an existing third-party > library called IntentKit [3] that includes a number of application > schemes that can be triggered by certain actions (e.g. "open in > browser"). Essentially, it attempts to recreate Android's intent > system. Adding ourselves to this library will make us compatible with > existing projects that use it, so I've filed a bug for this once we > release v1 [4]. If we promote IntentKit as the recommended method for > adding browser support, our third-party project might not need to be > fleshed out as much since IntentKit does that grudge work for us.
This seems much more Mozilla-y as a thing to do to me. Saying "please update your app to work specifically with our browser" is not only less open web, it's probably more of a hard sell than "please update your app so that it respect's the user's default browser preference". I assume we can't sideload IntentKit with Firefox? Gerv _______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
