Open Bug 1822013 Opened 2 years ago Updated 13 days ago

[ES][planetahuerto.es] Only the CC number autofill all the CC eligible fields and the preview/clear form/highlight works for the selected field only

Categories

(Toolkit :: Form Autofill, defect, P3)

Firefox 111
Desktop
Windows 10
defect

Tracking

()

Tracking Status
firefox111 --- disabled
firefox112 --- disabled
firefox113 --- disabled

People

(Reporter: ailea, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug, )

Details

Attachments

(7 files)

  • Screen recording of the issue in comment 1.

Found in

  • 111.0-candidates

Affected versions

  • 111.0-candidates

Tested platforms

  • Affected platforms: Windows 10

Preconditions

  • browser.search.region = ES
  • extensions.formautofill.creditCards.supportedCountries = ES
  • have an already saved CC in about:preferences

Steps to reproduce

  1. Reach the payment form on https://www.planetahuerto.es
  2. Click on any CC field and hover the mouse over any CC entry
  3. Click on the CC Number field and select a CC entry
  4. Click on the CC Number again and choose clear form
  5. Click on the CC Name field and select a CC entry
  6. Click on the expiry date field and select a CC entry

Expected result

  1. Preview should be applied on eligible fields.
  2. Choosing a CC entry from any CC fields should autofill all the CC eligible fields.
  3. Clear form dropdown should be displayed for the already autofilled fields and should clear all the CC eligible fields.
  4. The autofill highlight should be displayed for all the CC fields.

Actual result

  1. The preview is applied only for the selected field.
  2. All the CC fields are autofilled only if choosing a CC entry from the CC Number field. The CC number and expiry date fields will autofill only themselves.
  3. Clear form dropdown is displayed and clears only the selected field.
  4. The autofill highlight is displayed only for the CC number and expiry date fields if the autofill is triggered from those fields.
  5. The CC autofill dropdown is displayed for the already autofilled fields instead of the clear form dropdown.

Regression range

  • N/A

Additional notes

  • In Chrome, only the CC Name fields is working separately and it autofill only itself. The other fields are working as expected. The highlight is present in Chrome for all the fields.
  • Fathom Fox Sample
Depends on: 1815399
Priority: -- → P3

Hi Ailea, do we should preview highlight for the field that triggers autofill?

Flags: needinfo?(ailea)
Attached video 2024-03-27_14h42_24.mp4

Hi Dimi,
If I correctly understood your question, based on the demo/test page behavior (see the video attached to this comment), yes, the preview highlight should be applied to the field that triggers the autofill.

Flags: needinfo?(ailea)
No longer depends on: 1755033
Attached video 2024-03-27_15h27_28.mp4

The preview highlight is now displayed accordingly for the field that we trigger the autofill.

The Preview and Clear form will be triggered on card number + card name together and expiration date separately. The credit card name field is autofill when triggered from the credit card number or expiry date fields, but not viceversa (also, the values autofiled will not be treated as autofilled input). By setting extensions.formautofill.heuristics.autofillSameOriginWithTop to true Preview will be fixed, but the rest of the issue no.

I've retested this on the latest Nightly 132.0a1 on macOS 14.

  • Triggering autofill from “CC number” and “Date” fields is autofilling all fields
  • Clearing autofill from “CC number” and “Date” fields isn’t clearing “Name” field
  • Triggering autofill/clearing autoill from “Name” field is only autofilling “Name” field

When the extensions.formautofill.heuristics.autofillSameOriginWithTop setting is set to true, clearing autofill from any field is clearing all the targeted fields, but not if the triggered from "CC name" field.

The "CC Name" field is situated on the main page, and not inside an iframe, unlike the 'Card Number' and 'Expiry Date' fields which are located within same-origin iframes.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: