Open
Bug 1903008
Opened 3 months ago
Updated 11 days ago
[JP][rakuten.co.jp] Form preview, autofill and clear form aren't applied on all the eligible fields
Categories
(Toolkit :: Form Autofill, task, P3)
Tracking
()
NEW
People
(Reporter: hyacoub, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(3 files)
Found in
- Nightly 129.0a1
Affected versions
- Nightly 129.0a1
Tested platforms
- Affected platforms: macOS 14
Preconditions
- Install ja.JP Firefox build
- Use JP VPN
Steps to reproduce
- Reach the payment form on https://www.rakuten.co.jp/
- Click on "Name" field
- Select any of the options for the dropdown
- Right click on any of the fields and choose "Clear autofill form"
- Repeat steps from above for the rest of the fields
Expected result
- Form preview, autofill and clear form should be applied on all the eligible fields
Actual result
- Form preview, autofill and clear form aren't applied on all the eligible fields
Regression range
- N/A
Additional notes
- Autofill is working on Chrome but there are also issues.
Reporter | ||
Comment 1•3 months ago
|
||
Reporter | ||
Updated•3 months ago
|
Version: Firefox 128 → Firefox 129
Comment 2•3 months ago
|
||
This page has separate iframes for the expiry month and year.
Depends on: 1815399
Updated•3 months ago
|
Severity: S3 → N/A
Priority: -- → P3
Comment 3•13 days ago
•
|
||
As requested by the engineering team, I've retested this in the latest Nightly 132.0a1 on Windows 10 x64:
- The Card Number field is not cleared out when triggering autofill from the Cardholder Name field
The 'Name on Card' and 'Card Number' fields are situated on the main page, and not inside an iframe.
Setting the pref extensions.formautofill.heuristics.autofillSameOriginWithTop to true doesn't resolve the issue.
Please find attached the Field Info section details from about:autofill.
Comment 4•11 days ago
|
||
Removed the dependency, since there is no CC field located in any iframe. All the CC fields are part of the main frame.
No longer depends on: 1815399
You need to log in
before you can comment on or make changes to this bug.
Description
•