[US][nike.com] The State field is not captured in the Address Save/Update doorhanger
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
People
(Reporter: ailea, Assigned: janika)
References
(Blocks 1 open bug, Regression, )
Details
(Keywords: regression, Whiteboard: [fxcm-addr-compatibility])
Attachments
(3 files)
Found in
- Nightly 115.0a1 (2023-05-30)
Affected versions
- Nightly 115.0a1 (2023-05-30)
Tested platforms
- Affected platforms: Windows 10
Preconditions
- browser.search.region to US
- extensions.formautofill.addresses.capture.v2.enabled = true
Steps to reproduce
- Reach the address form on https://www.nike.com
- Fill in manually new Address info and submit the form
Expected result
- The complete address should be captured and stored with all the available info.
Actual result
- The State field (dropdown) is not captured in the Address save doorhanger and not saved in the Address manager.
Regression range
- N/A
Additional notes
-
The State field that is not captured in the save doorhanger is also NOT autofilled.
-
Not reproducible in Chrome, the State is captured in the save doorhanger and saved.
-
Fathom Fox Sample: https://drive.google.com/file/d/1nDI5tqC4RP1iKMFb1RJj4UGl9YQn_k8P/view?usp=share_link
Reporter | ||
Updated•1 years ago
|
Comment 1•1 years ago
|
||
:ailea, if you think that's a regression, could you try to find a regression range using for example mozregression?
Updated•1 years ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
This issue should be fixed by Bug 1836468
Reporter | ||
Comment 3•1 year ago
|
||
Unfortunately, I am still able to reproduce the issue in the latest Nightly build 117.0a1. The State field is still not captured in the Address save doorhanger and it is not saved in the Address Manager.
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Hi emilio,
In credit card/address autofill, when we run our heuristic to determine the type of a <input> or <select> field, we use checkVisibility
API first to filter out elements that are invisible[1].
However, when running checkVisibility
on the State field of the address form in nike.com, the API returns false. Could you help check whether this is expected? Thank you!
Comment 5•1 year ago
|
||
It is invisible, right?
.css-1jjxzuj select {
width: 100%;
box-sizing: border-box;
border-radius: var(--podium-cds-size-border-radius-s);
outline: 0px;
appearance: none;
opacity: 0;
}
(In particular the opacity: 0
)
It's just overlaid over the content.
Comment 6•1 year ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #5)
It is invisible, right?
indeed, thank you for checking!
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Set release status flags based on info from the regressing bug 1833618
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 8•1 year ago
|
||
This is fixed by Bug 1847687, because we now check a field's focusability instead of visibility when considering it for filling or capturing.
Updated•1 year ago
|
Reporter | ||
Comment 9•1 year ago
|
||
Verified - Fixed in the latest Nightly 120.0a1 (2023-10-19).
Description
•