Closed Bug 885587 Opened 11 years ago Closed 11 years ago

[Contacts] filterOp: match for filterBy: tel no longer matches non-normalized numbers

Categories

(Core :: DOM: Device Interfaces, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 883770

People

(Reporter: rwaldron, Unassigned)

References

Details

STR: 1. Create a contact with a non-normalized/internationaled number, eg. "8575409264" 2. Running the following code will result in an alert "0", where it previously would've matched the number to the contact. var request = navigator.mozContacts.find({ filterBy: ['tel'], filterOp: 'match', filterValue: '+18575409264' }); request.onsuccess = function onsuccess() { alert( this.result.length ); }; This is broken across the entire SMS/MMS app; numbers are no longer matching to contacts, which means no names appear in: 1. thread list view 2. thread-message view header 3. group participants view 4. group message header (new feature in branch)
Summary: [Contacts] filterOp: match for filterBy: tel no longer → [Contacts] filterOp: match for filterBy: tel no longer matches non-normalized numbers
So I flashed a new b2g18 build, created a contact with 8575409264, pasted your code in startup.js from SMS and I get 1.
Summary: [Contacts] filterOp: match for filterBy: tel no longer matches non-normalized numbers → [Contacts] filterOp: match for filterBy: tel no longer
Summary: [Contacts] filterOp: match for filterBy: tel no longer → [Contacts] filterOp: match for filterBy: tel no longer matches non-normalized numbers
Depends on: 883770
Assignee: nobody → dscravaglieri
blocking-b2g: leo? → leo+
Julien, I think it is. I tried the same "update a field in the contact" hack and that contact now appears.
Assignee: dscravaglieri → nobody
blocking-b2g: leo+ → leo?
Status: NEW → RESOLVED
blocking-b2g: leo? → ---
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.