Closed
Bug 1928367
Opened 1 year ago
Closed 1 year ago
[AU][boohooman.com] The Address autofill is working separately for two groups of fields
Categories
(Toolkit :: Form Autofill, task, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: ailea, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [fxcm-addr-compatibility] )
Attachments
(2 files)
Found in
- 134.0a1
Affected versions
- 134.0a1
Tested platform
- Windows 10
Preconditions
- Have set in about:config:
* browser.search.region - US
* extensions.formautofill.addresses.supportedCountries - AU
* extensions.formautofill.addresses.supported - ON
* Have an already saved address in about:preferences - Use Australia VPN
Steps to reproduce
- Go to https://www.boohooman.com/au and reach the shipping address form.
- Click on the First Name field and choose an address from the autocomplete dropdown.
- Click on the House Number and Street field and choose an address from the autocomplete dropdown.
Expected result
- All the address fields should be autofilled.
Actual result
- The address fields are autofilled separately. If the autofill is triggered from the first 4 fields, only those 4 fields are autofilled. If the autofill is triggered from one of the last 5 fields, only the last 5 fields are autofilled.
Regression range
- N/A
Additional notes
- Not reproducible in Chrome (see comment 1).
- Fathom sample.
| Reporter | ||
Comment 1•1 year ago
|
||
Autofill Chrome's behavior.
| Reporter | ||
Updated•1 year ago
|
QA Whiteboard: [QA-2708]
Updated•1 year ago
|
Severity: -- → N/A
Priority: -- → P3
Updated•1 year ago
|
Whiteboard: [fxcm-addr-compatibility]
Updated•1 year ago
|
Comment 2•1 year ago
|
||
I don't see any bug here any more. Likely this was fixed by other bugs, probably 1919742 or 1882480.
The only issue is that the address is filled into both address fields, whereas Chrome only fills into the second field, but I would consider filling in both to be more correct.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•1 year ago
|
||
Indeed, the issue was verified and as described in comment 2, it is no longer reproducible in the latest Nightly 137.0a1(2025-02-27).
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•