Closed
Bug 1149802
Opened 10 years ago
Closed 7 years ago
Phonenumberutils: Remove parseWithMCC and add functionality to fuzzyMatch
Categories
(Firefox OS Graveyard :: RIL, defect)
Firefox OS Graveyard
RIL
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: gwagner, Unassigned)
References
Details
(Whiteboard: [systemsfe])
+++ This bug was initially created as a clone of Bug #1136211 +++
+++ This bug was initially created as a clone of Bug #1136147 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/37.0.2062.120 Chrome/37.0.2062.120 Safari/537.36
Steps to reproduce:
Using Firefox OS 1.3 on a ZTE Open C with Build Identifier 20140523093151:
1. Open the SMS app, click the Compose icon.
2. In the "To:" field, enter any 15-digit phone number. I tried the iNum test number (see http://www.inum.net/test-sms-and-voice/ ), both as "883510000000094" and "+883510000000094". The results were the same in both cases.
3. Type a message in the Message box (I entered my email address).
4. Press Send.
Actual results:
The SMS application returned to an empty Compose screen and no message was sent.
Note that the results are the same if you first add a contact with the 15-digit phone number and attempt to send an SMS to that contact, rather than just typing the number into the "To:" field.
Expected results:
The SMS should have appeared in the message history of the SMS application, and the SMS should have been sent to the iNum test number. I know my carrier supports these, as I have sent an SMS to the iNum test number before with a different phone and it sent me an email indicating receipt.
It's possible this is related to https://bugzilla.mozilla.org/show_bug.cgi?id=899961 though they seem slightly different. Also, this issue happens with valid E.164 phone numbers, not just 20+-digit numbers.
Comment 1•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•