All of this isn't particularly relevant if the function is abysmally terrible at filling the correct fields with the correct data, which in the case of 1Passwor

All of this isn't particularly relevant if the function is abysmally terrible at filling the correct fields with the correct data, which in the case of 1Password certainly seems to be the case. In the example posted here, it happily completed fields for the credit card expiration year TWICE on the same form, one of which was pre-populated with a value that could not possibly have been a year. The apparent cause is because the substring 'year' appeared in the field name. Levenshtein distance of 12 for a 4 letter word? Yep, looks good! I mean, it's a result so certain there's no need to prompt the user, highlight changed fields or anything, right?