[FR][lvinted.fr] The autofill dropdown is not triggered and the autofill functionality is not working for the main address field
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
People
(Reporter: ailea, Unassigned)
References
(Blocks 2 open bugs, )
Details
Attachments
(1 file)
721.97 KB,
video/mp4
|
Details |
Affected Versions:
Nightly 99.a1, Beta 98 and Release 97
Tested on:
MacOS 11
Windows 10
Preconditions:
browser.search.region FR
extensions.formautofill.addresses.enabled - true
extensions.formautofill.addresses.supported to "detect"
extensions.formautofill.addresses.supportedCountries US,CA,FR
download latest Firefox Nightly with region locale
have a complete address already saved in about:preferences#privacy
Steps to reproduce:
- Reach the address form on vinted.fr
- Using the autofill feature, select 1 saved address entry from the autofill dropdown.
Expected Results:
- The address autofill dropdown should be displayed for all fields.
- All the fields should be successfully auto-filled.
- The first row of the address (from about:preferences) should be auto-filled in the "N et nom de rue" field and the second row in the Adresse ligne 2 (facultatif) field.
- City field should be highlighted with the autofill specific yellow color.
Actual Results:
- The address autofill dropdown is not displayed for "N et nom de rue" field.
- The "N et nom de rue" field is not auto-filled.
- The complete address is auto-filled in the Adresse ligne 2 (facultatif) field and the "N et nom de rue" field is not auto-filled at all (Chrome separates the address accordingly, see the video attached).
- City field is not highlighted with the autofill specific yellow color.
Notes:
- Reproducible on Chrome: No
Please let me know if separate bugs are needed for the issues described above.
- For the clear form issue please see bug 1753710. Randomly the clear form option is displayed and it works ok.
Reporter | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
This is reproducible on the English version of the vinted site (vinted.com). The issue is a combination of our heuristics for determining the autocomplete information for an element and their markup not having autocomplete attributes. For example, the address line inputs have an id of "line1" and "line2" and no autocomplete attributes. Because of this, we can't parse the autocomplete attribute to determine which fields these should map to so we rely on our heuristics.
The quick fix is to add "line1" and "line2" to our heuristicsRegexp.js for address-line1 and address-line2. This will allow autofill to work as expected, but the longer term fix is to increase awareness and understanding of the "autocomplete" attributes so web developers will know autocomplete will work as expected on their sites which should make users' experience on the site better.
Updated•3 years ago
|
Reporter | ||
Comment 2•1 year ago
|
||
Closing as worksforme since the issue described here is no longer reproducible in Nightly 125.0a1 (2024-03-01).
Description
•