Closed Bug 1526605 Opened 6 years ago Closed 6 years ago

autofill used my maiden name

Categories

(Toolkit :: Form Autofill, defect)

65 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: gygls73, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

I went to the roku site to order a new remote. I clicked the autofill on the shopping cart page, which did fill everything out as the program was programmed to do. This is a program I usually do not use. And have disabled from use. I also will not be using it again. My personal opinion is that this is a type of privacy breach.

Actual results:

However it used my MAIDEN name - which i have NOT used in almost 20 years. I'm not even sure how it got a hold of my maiden name - other than I had done a family name search a few weeks ago. And I forgot to do a history clean/ malware scan.

Expected results:

It should have autofilled with my married name

This appears to be working as designed -- if you entered your maiden name into a family search site it was probably tagged as a "name". Autofill offers you a choice of the previously encountered names (if the feature is enabled) but you get to see the choices on offer before you click it. So if you didn't want to use your maiden name then you wouldn't click autofill. Because you don't use Firefox much it had not had a chance to capture your married name anywhere. Once you submit correct information on the Roku site Firefox would have captured that profile and it would be an option in future pages. And of course you can always delete individual autofill entries or all of them (or turn the feature off) at any time in the preferences.

Group: firefox-core-security

I don't think this is a bug. As Dan said, this was probably entered somewhere else and stored by Firefox...

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Component: Untriaged → Form Autofill
Product: Firefox → Toolkit
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.