Closed Bug 1821019 Opened 2 years ago Closed 1 year ago

[IT][euronics.it] Autofill dropdown is applied/displayed on "Security code" field and considered as a CC field

Categories

(Toolkit :: Form Autofill, defect, P2)

Firefox 111
Desktop
Windows 10
defect

Tracking

()

VERIFIED FIXED
116 Branch
Tracking Status
firefox110 --- disabled
firefox111 --- disabled
firefox112 --- disabled
firefox116 --- verified

People

(Reporter: hyacoub, Assigned: dimi)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [fxcm-cc-new-geo])

Attachments

(2 files)

Attached video 2023-03-08_13h29_12.mp4

Found in

  • 111.0-candidates

Affected versions

  • 111.0-candidates

Tested platforms

  • Affected platforms: Windows 10

Preconditions

  • browser.search.region = IT
  • extensions.formautofill.creditCards.supportedCountries = IT
  • Have at least one CC already saved

Steps to reproduce

  1. Reach the payment form on https://www.euronics.it/
  2. Click on "Security Code" field

Expected result

  • "Security code" field shouldn't be considered a CC number field.

Actual result

  • Autofill dropdown is applied/displayed on "Security code" field and considered as a CC field.
  • "Clear Autofill Form" is applied also on "Card Number" field.

Regression range

  • Not a recent regression.

Additional notes

  • Not reproducible on Chrome.
Priority: -- → P2
Whiteboard: [fxcm-cc-new-geo]

This happens because the security code field

<input type="text" class="form-control securityCode mat-input" id="securityCode"
name="dwfrm_billing_creditCardFields_securityCode" required="" aria-required="true" value="" maxlength="4">

matches this regexp (add)?(?:card|cc|acct).?(?:number|#|no|num|field)"
https://searchfox.org/mozilla-central/rev/e77d89c414eac63a295a2124600045775a6f4715/toolkit/components/formautofill/shared/HeuristicsRegExp.sys.mjs#525

This issue will be fixed in Bug 1825777 by not running regexp-based heuristics for fields that we use fathom already.

Assignee: nobody → dlee
Status: NEW → ASSIGNED

We do not intend to capture or autofill Card Security Code (CSC) fields.

The reason for adding "cc-csc" support is to enhance the accuracy of our heuristics.
For instance, if a credit card form contains a CSC field that aligns with both "cc-number"
and "cc-csc" heuristics, we would only classify the field as a "cc-number" field
without the application of the cc-csc heuristic. However, if we include the
cc-csc heuristic, we can use the results as a hint that this field might not be a "cc-number"
field.

Attachment #9336995 - Attachment description: Bug 1821019 - Support classifying cc-csc fields, but refrain from capturing or autofilling cc-csc fields r=#credential-management-reviewers,mtigley → Bug 1821019 - Support classifying cc-csc fields, but refrain from capturing or autofilling cc-csc fields r=#credential-management-reviewers
Pushed by dlee@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a1b004d47efb Support classifying cc-csc fields, but refrain from capturing or autofilling cc-csc fields r=mtigley,credential-management-reviewers
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
Flags: qe-verify+

Verified - Fixed in latest Nightly 116.0a1 (15-06-2023). The autofill dropdown is no longer triggered for the Security Code field.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: