Closed Bug 982056 Opened 11 years ago Closed 7 years ago

[B2G][Contacts] Matching error when creating a new contact with the same first name and the beginning sequence of characters of the last name than an existing one

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: noemi, Unassigned)

Details

Description: Duplicate contact screen is shown when creating a new contact with the same first name and the beginning sequence of characters of the last name than an existing one STRs: 1) Select the Contacts app 2) Create a contact with first name: John last name: Anderson 3) Create a contact with first name: John last name: A Actual: Duplicate contacts screen is shown Expected: Duplicate contacts screen shouldn't be shown under those circumstances since: *There is no a exact match between the first name, last name *There is no a match between the beginning sequence of characters of the first name and absolute match with the last name Please refer to the active scenario specification for a more detailed information: pag 6 of https://bug875793.bugzilla.mozilla.org/attachment.cgi?id=786992 Environmental Variables: Device: Hamachi BuildId: 20140307120944 Platform version: 30.0a1 Gecko: 83c9562 Gaia: 5bc9b5c Repro frequency: 100%
The issue is reproduced also in v1.3 so setting ni to Jose Manuel and Ayman to clarify if it is a bug or there were changes during the implementation agreed with UX.
Flags: needinfo?(jmcf)
Flags: needinfo?(aymanmaat)
Version 1.3 BuildId: 20140311071817 Platform version: 28.0 Gecko-93e551e Gaia-8d235a2
From my PoV this is not how the active merge is supposed to work. Contact 1: (first name) John, (last name) Anderson (phone number) 123 Contact 2: (first name) John, (last name) A (phone number) 653 ...should not be offered as a match
Flags: needinfo?(aymanmaat)
...(oops pressed save too soon) therefore this is a bug.
this issue is due to how the Contacts API works, as in order to do a case insensitive match you need to specify the 'startsWith' filterOp that also makes partial, prefixed matchings. so, I think this is a minor issue, not blocking, and in any case would require a fix on platform side. best
Flags: needinfo?(jmcf)
Just adding some additional info about the failing scenarios: 1) Create John Anderson 2) Create John A 3) Duplicate found screen appears (It shouldn't, scenario described in comment 0) 4) Cancel duplicate contact found screen 5) Edit John Anderson contact and select Find duplicate contacts -> duplicate contact found screen is not shown (expected behavior) 6) Edit John A contact and select Find duplicate contacts->duplicate found screen is shown (it shouldn't)
(In reply to Jose M. Cantera from comment #5) > this issue is due to how the Contacts API works, as in order to do a case > insensitive match you need to specify the 'startsWith' filterOp that also > makes partial, prefixed matchings. so, I think this is a minor issue, not > blocking, and in any case would require a fix on platform side. > > best Reuben, could you please shed some light on the platform side?. Thanks!
Flags: needinfo?(reuben.bmo)
It sounds like the Contacts app should be checking if the results of the find() call are actually dupes? The filter is called startsWith, so that's what it does. We could also add an "equalsCaseInsensitive" index.
Flags: needinfo?(reuben.bmo)
In other words, please file a Contacts bug if the current mechanism is not enough to implement this feature.
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.