We do something like that to determine whether to show the android button in 
the url bar. Most apps doing what you want use custom protocols. I.e. 
Wallet://foo/

Wes



> On Feb 16, 2015, at 6:56 AM, Axel Nennker <[email protected]> wrote:
> 
> How about using one of these
> http://developer.android.com/reference/android/content/pm/PackageManager.html#queryIntentActivities%28android.content.Intent,
>  int%29
> http://developer.android.com/reference/android/content/pm/PackageManager.html#resolveActivity%28android.content.Intent,
>  int%29
> 
> with Intent intent = new Intent(ACTION_VIEW, new 
> URI.parse("https://www.mozilla.org";));
> to determine all the browsers on the system?
> Then create another intent for the current "link" like e.g. 
> "https://wallet.local/"; and repeat the above and then filter out all the 
> browsers.
> If there is one non-browser left then use that.
> If there are more non-browsers then let Android handle the intent resolution 
> and user UI.
> If there are no non-browsers then use Fennec.
> 
> 
> 
> 
> 2015-02-14 4:12 GMT+01:00 Richard Newman <[email protected]>:
>> OK. This isn't a case that Firefox's intent handling was designed to handle 
>> — it's a page that doesn't actually load.
>> 
>> That's unusual. Consider something like https://play.google.com, which is 
>> handled by the Play Store app.
>> 
>> I suppose there are two things we can do here:
>> 
>> 1. Show you the error page, but still check to see if there's an app. That's 
>> not pretty, but at least you'll be able to tap the app affordance.
>> 2. Do something less ugly, like show an affordance bar at the top: "this 
>> page didn't load, but here's an app that claims to handle this URL".
>> 
>> What do you expect to happen here, Axel?
>> 
>>> On Fri, Feb 13, 2015 at 6:57 PM, Axel Nennker <[email protected]> wrote:
>>> https://n2v3.e1.i3alab.net/HSVTicket3/Account/Login.aspx?ReturnUrl=%2fHSVTicket3%2f
>>> 
>>> Tap the lower "Einloggen" next to the wallet. Allow the popup.
>>> 
>>>> On Feb 14, 2015 12:17 AM, "Richard Newman" <[email protected]> wrote:
>>>> Let me see if I can clarify your question.
>>>> 
>>>> You're opening
>>>> 
>>>>   https://wallet.local/discovery
>>>> 
>>>> in Fennec, and you're not seeing the little Android icon appear in the URL 
>>>> bar?
>>>> 
>>>> Or you are seeing the little Android icon, but tapping it doesn't work?
>>>> 
>>>> Or you're seeing it, but you're expecting your app to launch immediately 
>>>> instead of the page opening in Fennec?
>>>> 
>>>>> On Fri, Feb 13, 2015 at 12:01 PM, Axel Nennker <[email protected]> 
>>>>> wrote:
>>>>> Hi,
>>>>> 
>>>>> we have an app that we expect to be launched because it is registered to 
>>>>> several intent filters.
>>>>> 
>>>>> This one is not working in Fennec:
>>>>>             <intent-filter>
>>>>>                 <action android:name="android.intent.action.VIEW" />
>>>>>                 <category android:name="android.intent.category.DEFAULT" 
>>>>> />
>>>>>                 <category 
>>>>> android:name="android.intent.category.BROWSABLE" />
>>>>>                 <data android:host="wallet.local" 
>>>>> android:path="/discovery" android:scheme="https" />
>>>>>             </intent-filter>
>>>>> 
>>>>> This mechanism works in Chrome but not in Nightly.
>>>>> 
>>>>> Not sure what the right way to launch an app is.
>>>>> We have another version that is registered to a custom url scheme but I 
>>>>> thing the filter above should work in Firefox too.
>>>>> 
>>>>> I know there is an ongoing discussion about webintents, webactivities, 
>>>>> chromes native messaging etc and "the right way" but I think that the 
>>>>> above filter should work in Fennec.
>>>>> So is this a bug or was conscious decision not to let android handle 
>>>>> https events even if an app is registered for it?
>>>>> 
>>>>> cheers
>>>>> Axel
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> mobile-firefox-dev mailing list
>>>>> [email protected]
>>>>> https://mail.mozilla.org/listinfo/mobile-firefox-dev
>>>>> 
>>>> 
>> 
> 
> _______________________________________________
> mobile-firefox-dev mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/mobile-firefox-dev
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev

Reply via email to