[LINUX] Credit Card Autofill does not Autofill
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
People
(Reporter: scot.mcpherson, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0
Steps to reproduce:
Payment information is saved and saved correctly.
On any payment processing page, when choosing to autofill with a saved payment method, the choice is made available, and while hovering over the payment choice the payment fields are populated correctly, however once the choice has been selected the payment fields are blanked.
Actual results:
Payments are never filled after payment choice has been made.
Expected results:
Payment information should populate the payment fields.
| Reporter | ||
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Form Autofill' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•1 year ago
|
||
Hi Scot, thank you for reporting this issue and providing the detailed information.
Could you help take a look regarding whether you can see the credit card number when editing the credit card number in the setting page?
If you are not sure how to navigate to the editing page, see Here. Really appreciate for the help!
| Reporter | ||
Comment 4•1 year ago
|
||
Yes, I can see the card information and it is correct.
I can also edit the card number and information on the settings page (though it fails to validate, which is correct)
Comment 5•1 year ago
|
||
I think this has just started occurring for me on Windows as well.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0
Don't have a lot of data to provide unfortunately, was not keeping track of this until now. Just had it fail on the Google Webpass payment form, but I'd never used that until today, so it could be a site issue. I've also had at least one other site fail in the same way that I know worked before, but I thought it was a site issue as well so I didn't make a note of the name.
The reason I'm reporting is just because it's the exact issue described above, where the data appears until I click, then disappears. I don't recall having ever seen that since I started using autofill. The usual failure mode when a site has e.g. bad JS behavior is that fields don't fill at all, so this stood out to me.
Updated•1 year ago
|
| Reporter | ||
Comment 6•7 months ago
|
||
Just a little updated information
I am currently using 149.0.2+linuxmint1+zena on Linux Mint, a system package not a FlatPack.
This issue persists through all updates since I posted the original bug report for 133.
| Reporter | ||
Comment 7•6 months ago
|
||
Johannes [:joschmidt] on bug https://bugzilla.mozilla.org/show_bug.cgi?id=2026488
Okay, then it's most likely the OSKeyStore:
The key stored in the OSKeyStore was probably overwritten. There could be several reasons for this.
In the past, we had a code path that caused keys in the OSKeyStore to be reset (i.e., regenerated and overwritten) even if they were only
temporarily unavailable. This has recently been fixed afaik in D243156. However, this fix does not help users whose keys were overwritten
previously. In these cases, the credit card information unfortunately needs to be re-entered.
We are currently in the process of consolidating the local persistence layer and will also improve Autofill as part of this effort. Until then, we
apologize for the - admittedly frustrating - inconvenience.
We are tracking these issues in 1755786 - the title might not be appropriate anymore.
Confirmed, this does in fact seem to work now.
Steps taken to validate.
-
go to Settings > Privacy & Security > Manage Payment Methods -
Remove Cards -
Close all Mozilla application instances (I don't know if this is required, I just did it to clear any running cache or running unlocked keyrings) -
Start Firefox -
Settings > blah blah blah -
Add new card -
test on a vendor site never visited before (to avoid site caching and cookies)
| Reporter | ||
Comment 8•5 months ago
|
||
Unfortunately another user on https://bugzilla.mozilla.org/show_bug.cgi?id=2026488 discovered the fix does NOT persist after a reboot.
I have confirmed it.
This bug is still a problem.
Description
•