[HomeDepot] Autofilled CC number field will be cleared out after selecting a different Exp date
Categories
(Toolkit :: Form Autofill, defect, P2)
Tracking
()
People
(Reporter: tbabos, Unassigned)
References
(Blocks 2 open bugs, )
Details
Attachments
(1 file)
510.56 KB,
video/mp4
|
Details |
Affected version:
All - if CC specific prefs are enabled
Tested on:
Windows 10
MacOS 10.13
Ubuntu 16.04
Steps to reproduce:
- Reach the payment form on homedepot.com
- Autofill the CC number field (exp date will also be autofilled)
- Manually select a different date for Exp.
- Click again on the CC number field
Expected results:
- CC number field should not change unless the user clears out the field or selects Clear Form from the autofill dropdown
Actual results:
- CC number field is cleared out and Clear Form option no longer works for this field.
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Updating whiteboard tag for team triage.
![]() |
||
Updated•5 years ago
|
![]() |
||
Updated•5 years ago
|
Comment 2•5 years ago
|
||
The severity field is not set for this bug.
:MattN, could you have a look please?
For more information, please visit auto_nag documentation.
![]() |
||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
This bug as reported isn't specific to autofill. You can reproduce this experience by doing the following:
- Disable credit card autofill
- Navigate homedepot.com to the guest checkout flow
- Enter a credit card number into the credit card number field (e.g., 4111 1111 1111 1111)
- Click on any other field (e.g., "Billing Address / Address Line 1")
- Click on the credit card number field again
You'll see that the previously-entered number is wiped out and needs to be re-entered. This is Home Depot's chosen user experience. It is horrible and incredibly user-hostile, but there's not much we can do to fix Home Depot's bad UX choices.
I have noticed another behavior related to this that is a problem with autofill, and will be filing a separate bug on it; but I think this issue should be closed as invalid.
Comment 4•5 years ago
|
||
The aforementioned problem has been filed as Bug 1649304
![]() |
||
Comment 5•5 years ago
|
||
Web site designed it this way. Works as expected.
![]() |
||
Updated•5 years ago
|
Updated•5 years ago
|
Description
•