Open
Bug 1956464
Opened 1 month ago
Updated 7 days ago
[CA][etsy.com/ca] Address Fields not autofilled after changing Country
Categories
(Toolkit :: Form Autofill, task)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox138 | --- | affected |
People
(Reporter: epopescu, Unassigned)
References
()
Details
Attachments
(2 files)
Found in
- Nightly 138.0a1
Affected versions
- Nightly 138.0a1
Tested platforms
- Affected platforms: All
Prerequisites
- use CA VPN
- install en-CA build
- set browser.search.region = CA in about:config
Steps to reproduce
- Go to https://www.etsy.com/ca/ and add an item to cart
- Proceed to checkout and autofill the address
- Click the Country dropdown and select a different country
- Attempt to autofill the form by selecting a saved address from the autofill dropdown
Expected result
- All fields are autofilled correctly.
Actual result
- Some fields remain empty randomly after using autofill again.
Regression range
- N/A
Additional notes
- The issue does not occur in Chrome, where fields are autofilled but not highlighted.
- When the two prefs extensions.formautofill.heuristics.detectDynamicFormChanges and extensions.formautofill.heuristics.fillOnDynamicFormChanges are enabled, the autofill dropdown no longer appears in the fields. Please see this recording.
- Please see Fathom Fox page, but couldn't save the screenshot-www.etsy.com.
Reporter | ||
Comment 1•1 month ago
|
||
Reporter | ||
Comment 2•1 month ago
|
||
Reporter | ||
Updated•1 month ago
|
Has STR: --- → yes
QA Whiteboard: [QA-3488]
status-firefox138:
--- → affected
OS: Unspecified → All
Hardware: Unspecified → Desktop
Version: unspecified → Firefox 138
Comment 3•1 month ago
|
||
This behavior is also reproducible on the US version of Etsy (www.etsy.com).
Comment 4•7 days ago
|
||
A form-changed
gets dispatched with reason visible-element-became-invisible
for each field but it's ignored because each element is already disconnected. In this case we expect a following form-changed
event including the reason nodes-removed
, which we would then handle, but we don't detect any further form change (no further form-changed
event).
Depends on: 1955252
Updated•7 days ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•