+++ This bug was initially created as a clone of Bug #898364 +++ Please see bug 898364, comment #5 for the objective. The PhoneNumberUtils API could be a very useful API for lots of communication apps, including messaging, telephony and contacts. We're hoping to expose this API to the content because: 1. We don't want each app to load one duplicated PhoneNumberUtils.jsm copy which will redundantly occupy the memory. 2. Some of the utility functions in PhoneNumberUtils.jsm need to refer to the RIL info. For example, parseWithMCC(aNumber, aMCC) needs MCC. Therefore, keeping PhoneNumberUtils.jsm in the parent makes more sense. In the initiative step, we only want this API for certified apps only.
Has there been any discussion regarding the standardization of a common Web API for phone number normalization?
Rick> not that I know of.
It seems there has already been a similar work at Bug 883923?
Fuzzy Matcher is quite different, it's only do handle comparison. We try hard to not expose the whole PhoneNumberUtils API and try to extract meaningful API instead :)
OK, I see. Thanks! It's great to have an existing framework to expose other APIs in the future.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.