Closed
Bug 1956492
Opened 1 year ago
Closed 11 months ago
[DE][springlane.de] The postal code and city fields are not correctly autofilled or not autofilled if the form is autofilled after the Country is changed
Categories
(Toolkit :: Form Autofill, task)
Tracking
()
VERIFIED
FIXED
People
(Reporter: ailea, Unassigned)
References
()
Details
(Whiteboard: [fxcm-addr-compatibility])
Attachments
(5 files)
Found in
- 138.0a1
Affected versions
- 138.0a1
Tested platform
- Windows 10, macOS 12, Ubuntu 20
Preconditions
- Have set in about:config:
- browser.search.region - DE
- Have an already saved address in about:preferences
Steps to reproduce
- Go to https://springlane.de/ and reach the shipping address form.
- Change the Country from the dropdown to e.g Italy
- Click on any field and choose an address from the autocomplete dropdown.
Expected result
- All the fields should the autofilled accordingly.
Actual result
- The Postal Code field is autofilled but not highlighted and the wrong dropdown is displayed if you click on it, and the City field is not autofilled at all. The behavior is not the same all the time, sometimes both postal code and city fields are autofilled bug not highlighted and the wrong dropdown is displayed for both of them, sometimes both fields are not autofilled at all.(see the video attached in the description and the videos attached in comment 1 and comment 2 as well.)
Regression range
- N/A
Additional notes
- The issue is reproducible using the dynamic form support prefs to both true or false.
- Downloaded page.
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
| Reporter | ||
Comment 2•1 year ago
|
||
| Reporter | ||
Comment 3•1 year ago
|
||
| Reporter | ||
Comment 4•1 year ago
|
||
Comment 5•11 months ago
|
||
As of Fx139 address autofill is supported in US,CA,FR,GE,GB by default. The supported country options on sprinlane.de are FR and DE. Changing the country value from either FR to DE or from DE to FR during autofill works as expected.
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
| Reporter | ||
Comment 6•11 months ago
|
||
Verified in 139.0a1 (2025-04-22) and I got the behavior described in comment 5. Based on the expected result, I will mark this accordingly.
Status: RESOLVED → VERIFIED
status-firefox138:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•