Open
Bug 1756135
Opened 3 years ago
Updated 2 years ago
[US][wish.com] The state dropdown field is not auto-filled if the country selected is US
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
NEW
People
(Reporter: ailea, Unassigned)
References
(Blocks 2 open bugs, )
Details
Attachments
(3 files)
Affected Versions:
Nightly 99.a1, Beta 98 and Release 97
Tested on:
MacOS 11
Windows 10
Preconditions:
browser.search.region US
extensions.formautofill.addresses.enabled - true
extensions.formautofill.addresses.supported to "detect"
extensions.formautofill.addresses.supportedCountries US,CA
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 wish.com
- Using the autofill feature, select 1 saved address entry (make sure that Country/Region is US).
- Click on the Country/Region and select a Country different from US.
- Using the autofill feature, select 1 saved address entry.
Expected Results:
- All the fields should be successfully auto-filled.
- The Country should be auto-filled accordingly (changed to US).
Actual Results:
- If the country selected is United States, the State/Province dropdown is not auto-filled. If another country is selected the State/Province field becomes input field (not dropdown as it is when US is selected as Country) and it is auto-filled correctly.
- If another country than US is selected, by using the auto-fill, the Country is not accordingly changed to US (the Address Country saved in about:preferences).
Notes:
Reproducible on Chrome: Yes
Updated•3 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Whiteboard: [fxcm-addr-compatibility]
Updated•2 years ago
|
Comment 1•2 years ago
|
||
The "State" and "Country" dropdown are not auto-filled because those fields are implemented with a <div>, not a <select> and we only autofill <input> and <select> now.
Whiteboard: [fxcm-addr-compatibility]
Comment 2•2 years ago
|
||
The issue isn't fixed, the same behaviour is reproducing on Firefox Nightly 115.0a1 (2023-05-25) also.
Comment 3•2 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•