Open Bug 1897199 Opened 6 months ago Updated 5 months ago

[KE][mydawa.com] The credit card CVV field is considered as password field

Categories

(Toolkit :: Form Autofill, task, P3)

Desktop
All
task

Tracking

()

Tracking Status
firefox126 --- disabled
firefox127 --- disabled
firefox128 --- disabled

People

(Reporter: ailea, Unassigned)

References

(Blocks 1 open bug, )

Details

Attachments

(1 file)

Attached video 2024-05-16_17h14_51.mp4

Found in

  • 128.0a1 (2024-05-16)

Affected versions
N/A

Tested platforms

  • Affected platforms: Windows 10, macOS 12, Ubuntu 20

Preconditions

  • browser.search.region US
  • Have at least one CC already saved

Steps to reproduce

  1. Reach the payment form on https://mydawa.com
  2. Click on the CVV field.
  3. Fill in the CVV field.

Expected result
No dropdown should be displayed for the CVV field.

Actual result
The password manager dropdown is displayed in the CVV field and the password manager doorhanger is displayed if the CVV field is filled using the CVV field value as password.

Regression range

  • Not a recent regression.

Additional notes

The same issue is also reproducible on https://www.jamboshop.com since both websites are using the same payment webpage.

The CVV field has type="password". The form has five fields:

card number - identified as the card number correctly
card expiry - identified as the expiry correctly
cvv - ignored as a credit card field and the password manager thinks it is a password
names - incorrectly identified as the credit card year
country - not identified as anything

If I remove the type="password", the CVV field is correctly identified, but the names field is no longer identified as anything. The country is ignored in both cases.

Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: