[IT][philips.it] Autofill is triggered from an address number field
Categories
(Toolkit :: Form Autofill, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox111 | --- | unaffected |
firefox112 | --- | unaffected |
firefox113 | --- | disabled |
firefox114 | --- | disabled |
firefox115 | --- | disabled |
firefox116 | --- | verified |
People
(Reporter: hyacoub, Assigned: dimi)
References
(Blocks 1 open bug, )
Details
(Keywords: regression, Whiteboard: [fxcm-cc-new-geo])
Attachments
(2 files, 1 obsolete file)
Found in
- 113.0a1
Affected versions
- 113.0a1
Tested platforms
- Affected platforms: Windows 11 and macOS 11
Preconditions
- browser.search.region = IT
- extensions.formautofill.creditCards.supportedCountries = IT
- Have at least one CC already saved
Steps to reproduce
- Reach the payment form on https://www.philips.it
- From the delivery address click on "Numero Civico" field
Expected result
- Autofill shouldn't be triggered from an address number field
Actual result
- Autofill is triggered from an address number field
Regression range
Additional notes
- Not reproducible on Chrome.
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
This seems to be happening because we're only gathering credit card fields as a possibility for field names here
Then, when fathom can't recognize the field, we try to match against another set of autofill rules. Specifically, we're matching against this element string: "Numero civico*"
.
Interestingly, if we add "IT" as a supported region to extensions.formautofill.addresses.supportedCountries
then the form autofill address fields are included. And somewhere down the line form autofill determines the house number field is NOT a CC number field and the dropdown doesn't show as a result.
I haven't quite determined where this is yet. Dimi, could you point to where this branch is happening?
Updated•2 years ago
|
Comment 2•2 years ago
|
||
After discussing with Dimi, we can just remove this regular expression:. This is fine since this was added before we had Fathom to identify CC name and CC number fields and is a more relaxed heuristic that isn't necessary anymore.
Assignee | ||
Updated•2 years ago
|
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
Assignee | ||
Comment 4•1 year ago
|
||
At present, we don't execute address field identification for regions that don't support
address autofill. However, this impacts the accuracy of identifying credit card fields too.
This is due to the fact that if a field appears to be both an address and a credit card field,
we will consistently regard it as a credit card field if we don't execute address field heuristics.
This patch guarantees that we run both address and credit card heuristics when form autofill
is enabled for a region. We will still not autofill or capture address fields for regions
that do not support address autofill.
Depends on D179688
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
bugherder |
Comment 7•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
The patch landed in nightly and beta is affected.
:dimi, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox115
towontfix
.
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 9•1 year ago
|
||
Verified - Fixed in latest Nightly 116.0a1 (2023-06-15). The autofill dropdown is no longer triggered for Numero Civico field.
Assignee | ||
Updated•1 year ago
|
Description
•