Saved addresses are not autofilled on Amazon.com
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
People
(Reporter: csasca, Unassigned)
References
(Blocks 1 open bug)
Details
Affected versions
- Firefox 86.0b9
- Firefox 87.0a1
Affected platforms
- macOS 11.2.1
- Ubuntu 20.04
Steps to reproduce
- Launch Firefox
- Have at least 1 address saved in "Forms and Autofill"
- Access Amazon and login with a valid account
- Click on Account and select "Your Addresses"
- Click on Add Address
Expected result
- Credentials from the saved address is autofilled
Actual result
- The user is unable to autofill the saved address
Regression range
- Will see for a regression.
Additional notes
- Only Windows doesn't seem to be affected and autofills the saved address on Amazon.
- The issue can be seen in the following attachment
- Seems that Walmart.ca is affected too
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Comment 1•3 years ago
|
||
This doesn't seem to be a regression. Tried going as far as Firefox 56.0a1 and the issue was still present.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
FYI1: autocomplete attribute on input fields has non-standard value
FYI2: might worth to check German/French version of Amazon to see if it works differently there
Comment 3•3 years ago
|
||
(In reply to Sergey Galich from comment #2)
FYI1: autocomplete attribute on input fields has non-standard value
For reference, most elements on the "Add a new Address" page have an ID that contains "address-ui-widgets-enterAddress<value>" where <value> can be "FullName", "Line1", "Line2", "City", etc.
FYI2: might worth to check German/French version of Amazon to see if it works differently there
The markup is identical on the German, French, and Spanish versions of Amazon so address autofill doesn't work as expected on these sites either.
I originally thought that the issue was missing rules in heuristicsRegexp.js, but it seems like we aren't referencing these heuristics when searching through address fields. While we do have _parseAddressFields which have their own additional address line regular expressions, we end up terminating early due to the field details not having a fieldName associated with them. It seems like we aren't getting the autocomplete information we need from the element itself which makes sense to me. The autocomplete values used by the site don't match up with the autofill spec so I don't think the input element would know how to parse this non-standard information.
Also, you can partially autofill on this address form on Chrome, only the name and phone number fields seem to work. I'm not sure what we can do in this case
Comment 4•3 years ago
|
||
I wonder if it was a deliberate decision on Amazon's part to not add the autocomplete attributes? Or maybe it just didn't occur to them. The question is, do we think there's enough value to our users to try and recognize this as an address form despite that.
Comment 5•3 years ago
•
|
||
Just for additional context, autofilling addresses work as expected on Safari on Amazon. Autofill works partially on Edge, filling out name, phone number, and state correctly.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•