Open Bug 1904112 Opened 5 months ago Updated 4 months ago

[CH][www.digitec.ch]CC Expiry Date not being stored on Privacy Settings page

Categories

(Toolkit :: Form Autofill, task, P3)

Firefox 129
task

Tracking

()

Tracking Status
firefox127 --- disabled
firefox128 --- disabled
firefox129 --- disabled

People

(Reporter: epopescu, Unassigned)

References

(Blocks 1 open bug, )

Details

Found in

  • Nightly 129.0a1

Affected versions

  • Nightly 129.0a1

Tested platforms

  • Affected platforms: Windows 10

Preconditions

  • Install the Firefox en-US build
  • set following prefs:
    extensions.formautofill.creditCards.supported = on
    browser.search.region = CH
  • Use CH VPN to test
  • Have at least one CC saved in about:preferences#privacy

Steps to reproduce

  1. Third-party sign into https://www.digitec.ch/, add an item to cart and navigate to checkout page
  2. Use the autofill, preview and clear form within the CC form

Expected result

  • Autofill, preview and clear form options in the CC form are working as expected.

Actual result

  • Expiry year is not previewed, autofilled or stored
  • There is no "Clear autofill form" option available
  • The fields are not highlighted when autofilled

Regression range

  • N/A

Additional notes

  • Most of these issues, except the Expiry Year not being stored, previewed or autofilled, can be reproduced in Google Chrome.
  • Fathom Fox
Priority: -- → P3
Severity: -- → N/A
Depends on: 1904593

I've tested again in the latest Nightly 130.0a1 build on Windos10 x64. Although most of the issues mentioned here are no longer reproducible, one issue remains: the Expiry Date is not being stored. Should I log a separate issue for this? Thanks

I think you can just reuse this bug and change the title. It is probably the same issue as 1904097.

Title updated based on Comment 2. Thanks

Summary: [CH][www.digitec.ch]Multiple issues with Autofill Preview and Clear Form options in CC form → [CH][www.digitec.ch]CC Expiry Date not being stored on Privacy Settings page
You need to log in before you can comment on or make changes to this bug.