STR: 1. Visit https://maps.google.com in Firefox OS Browser, on a phone. 1. Get to the Google Maps page for some business with a phone number, e.g.: - Type "Mozilla" into the maps search field - Tap the result in the dropdown menu for Mozilla on East Evelyn - Tap the bottom bar that says "Mozilla [4.5 stars] [43 reviews]" 2. You should see buttons for "CALL" and "WEBSITE". Tap the "CALL" one. ACTUAL RESULTS: A blank browser-window opens up. No indication of what the phone number is anywhere. EXPECTED RESULTS: Dialer should be opened with phone number entered. This basically breaks the use-case of using Google Maps to find a business's phone number, because they don't actually display the phone number in their mobile UI -- they just have the "CALL" button. I'm not sure what component this belongs in. Starting out in Firefox OS | General.
I'm using a Flame device, on the Firefox OS 2.1 channel. Git commit info: 2015-01-08 07:34:23 ed2e2787
doug, should this work?
(In reply to Daniel Holbert [:dholbert] from comment #1) > I'm using a Flame device, on the Firefox OS 2.1 channel. FWIW: I've repro'd this on a Flame with a mid-december Firefox OS 2.2 Nightly, too. So, not a 2.1-specific issue. Also: in Yelp's webapp, this *works correctly*. (When you tap a "call" button in Yelp, the dialer is launched, and the number is pre-entered.) I used "Mountain View Public Library" for testing Yelp. I tried the library in Google Maps as well, just to double-check that this is still broken there -- it is.
Summary: "Call" button on Google Maps just opens up a blank page → "Call" button on Google Maps just opens up a blank page. Works in Yelp. (e.g. for Mountain View Public Library)
Summary: "Call" button on Google Maps just opens up a blank page. Works in Yelp. (e.g. for Mountain View Public Library) → "Call" button on Google Maps just opens up a blank page. (e.g. for Mountain View Public Library) (Yelp works correctly)
One more data point: Google Maps' call button apparently works correctly in Firefox on Android. (AaronMT was good enough to test this for me) So, that means Google's not relying on anything webkit-specific for this, or anything like that. There seems to be a FxOS-specific problem with handling this.
Here are the formats of the links that each website provides: Yelp -- tel:+123 Google Maps -- tel://+123 Thus it looks to me like an issue with associations. I'm not sure who would know more about this, or where it's configured. I'm bringing in Fabrice because I have some vague inkling that he would either know about this, or whom to ask.
Flags: needinfo?(drs.bugzilla) → needinfo?(fabrice)
The url used by Google is not conform to the rfc 2806  that is implemented by the tel: uri parser . That means that we end up throwing when creating the channel at http://mxr.mozilla.org/mozilla-central/source/b2g/components/TelProtocolHandler.js#51  https://www.ietf.org/rfc/rfc2806.txt  https://mxr.mozilla.org/mozilla-central/source/b2g/components/TelURIParser.jsm
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.