1495882 - Remove existing duplicate entries

Status: NEW

(Toolkit :: Form Autofill, enhancement, P3)

Description

[Jared Wein [:jaws] (please needinfo? me)]

During form autofill initialization we should kickoff a task that will remove duplicate entries.

Comment 1

[Matthew N. [:MattN]]

Is bug 1485881 the wrong bug?

Comment 3

[Matthew N. [:MattN]]

Some of the other ideas/problems we looked at:

• line formatting
  • abbreviations
    • St. vs. Street vs St versus none-at-all
    • Ave. vs. Avenue
    • N. vs. North
• Don’t auto-save addresses, show a doorhanger instead
• Prefixes in name field (not sure if real issue)
• Intersection saved from craigslist
• telephone numbers (not sure if real issue)
• do we normalize with PhoneNumber.jsm before comparing to the stored version which is normalized?
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1407545
• email addresses
  • Some users use a different email address per domain/service with the same address
    • Gerv filed a bug on this
• initials in first or middle name fields
• Ignore Middle name for comparison? Maybe already done
• making sure address autofill appears on relevant fields
• looking for dupes even if autofill wasn’t used / show doorhanger
• Require address-line field in an auto-created address record
  • Maybe some countries don’t require it since a postal code is enough?

Comment 4

[Jeremy]

Came here from bug 1394931 with a similar concern in that I have one physical address but will use one of several email addresses depending on the form that is being filled (i.e. for mailing lists vs purchases for myself vs purchases for my business) and there is no way to know ahead of time which email address will be autofilled. This is more of a minor UX annoyance than a bug of severity, but still an annoyance.

Fundamentally, the form autofill collects two (well, two and a half, really) separate-but-related types of information

1. Unchanging Fields: Name, Street Address, City, State, Zip Code are all a unit together which would ostensibly either never change (which is why there are multiple autofills available) or all change together at once (e.g. if the user moves into a different home)

2. Variable fields: Phone, Email. These are fields that may be different even if all the fields from #1 are identical, and are not necessarily inherently dependent on anything from the first group to determine which variant the user wants to fill the form with.

For example:

• My work email + Work phone
• My work email + Cell phone
• My main personal email + Cell Phone
• An alternate Personal Email + Cell Phone

3. Organization which is in some middle ground in that it may be related to the first type, the second type, both or neither.

I have a couple of suggestions as to how this might be handled

• Surface and display where there are differences between otherwise identical Saved Addresses in the dropdown
• Allow for multiple email addresses and phone numbers per-Saved Address and a quick way to select which at dropdown.
• Enrich the Saved Addresses functionality to store a vCard's worth of data, which would allow for multiple emails-per-address and also make it slightly more portable, not that anyone has specifically asked for that. Maybe some elements from Thunderbird Address Book could be used?

Anyway, just wanted to expand and clarify.