Closed Bug 807069 Opened 12 years ago Closed 12 years ago

[Browser] tel: protocol not supported in B2G browser app

Categories

(Firefox OS Graveyard :: Gaia, defect)

Product:
Firefox OS Graveyard
Component:
Gaia
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 805282

People

(Reporter: dholbert, Unassigned)

References

(
URL
)

Details

(Keywords: b2g-testdriver, unagi) 

STR:
In Browser URL bar, type in
  tel:16509030800
and hit enter.  (That's the Mozilla MV office phone number, from the US / Canada)

EXPECTED RESULTS: Dialer should open, with that number already entered in for you.

ACTUAL RESULTS: Error page:
>  The address wasn't understood
>  tel is not a registered protocol
>  ----
>  You might need to install other software to open this address.
>  [Try Again]

My Firefox Nightly on Android gives EXPECTED RESULTS.
My B2G build from 10-24 gives ACTUAL RESULTS (buggy).


NOTE: this affects linkified phone numbers on the web.  I hit this bug when pressing contacts' phone numbers in the "Contacts" sub-page on https://m.gmail.com
Summary: [Browser] tel: protocol not supported in browser → [Browser] tel: protocol not supported in B2G browser app
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Can you try this bug again? This bug is probably related to Bug 805282 and the patch for it has been landed the 10-27.
Ah, nice. I'll try it again once I get an update. (I'm on dogfooding stable builds, and the last one was from 10-24)
Depends on: 805282
I believe this is a dup.

Here's a test page to try various things, dholbert: http://people.mozilla.com/~nhirata/html_tp/AndroidLinks.html
Yup -- the sms, tel, and mailto links there all give me "not a registered protocol".  Likely a dupe of bug 805282 -- I'll confirm when I get a build with that fixed.
An update to the stable channel should be given sometime soon.  Not sure exactly when.  We had a bug which caused it to be pulled yesterday.
I heard you should be getting a new build today.  I'll wait to hear from you, before doing anything, dholbert.  :)
Just got the update. This is WFM, so I'm going to assume it was fixed by bug 805282.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
blocking-basecamp: ? → ---
You need to log in before you can comment on or make changes to this bug.