Closed Bug 1836008 Opened 1 year ago Closed 1 year ago

[US][zara.com] "Address 2" field isn't captured in the doorhanger and isn't saved in the saved address from

Categories

(Toolkit :: Form Autofill, task, P3)

Firefox 115
Desktop
Windows 11
task

Tracking

()

VERIFIED FIXED
Tracking Status
firefox113 --- disabled
firefox114 --- disabled
firefox115 --- disabled

People

(Reporter: hyacoub, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [fxcm-addr-compatibility])

Attachments

(2 files)

Attached video 2023-05-31_11h42_15.mp4

Found in

  • Firefox Nightly 115.0a1

Affected versions

  • Firefox Nightly 115.0a1

Tested platforms

  • Affected platforms: Windows 11

Preconditions

  • Install en-US Firefox build
  • Use US VPN
  • browser.search.region = US
  • extensions.formautofill.addresses.capture.v2.enabled = true
  • extensions.formautofill.addresses.supported = on
  • Save 1 address with only MANDATORY fields filled in about:preferences#privacy, Forms & Autofill section

Steps to reproduce

  1. Reach the address form on https://www.zara.com/
  2. Fill in all the fields including the OPTIONAL ones(use same values saved in Preconditions in the MANDATORY fields), and submit the address form

Expected result

  • "Address 2" field should be captured in the doorhanger and saved in the saved address form

Actual result

  • "Address 2" field isn't captured in the doorhanger and isn't saved in the saved address form

Regression range

  • N/A

Additional notes

  • Couldn't trigger save address doorhanger on Chrome.
  • Autofill is applied on "Address 2" with "Address" field info.
Attached file zara.html
Summary: [US][zara.com] "Address 2" field isn't captured in the doorhanger and isn't saved → [US][zara.com] "Address 2" field isn't captured in the doorhanger and isn't saved in the saved address from

:hyacoub, if you think that's a regression, could you try to find a regression range using for example mozregression?

Severity: -- → S4
Depends on: 1836456
Priority: -- → P3
Whiteboard: [fxcm-addr-compatibility]

This issue should be fixed by Bug 1836456

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: qe-verify+
Resolution: --- → FIXED

I confirm that this issue isn't reproducible anymore on Firefox Nightly 117.0a1 (2023-07-18).

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: