Open Bug 1835799 Opened 1 year ago Updated 6 months ago

[CA][www.staples.ca] The Address Doorhanger is not displayed upon address form submission

Categories

(Toolkit :: Form Autofill, task, P3)

Desktop
Windows 10
task

Tracking

()

Tracking Status
firefox-esr102 --- disabled
firefox113 --- disabled
firefox114 --- disabled
firefox115 --- disabled

People

(Reporter: epopescu, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [fxcm-addr-compatibility])

Found in

  • Nightly 115.0a1

Affected versions

  • Nightly 115.0a1

Tested platforms

  • Affected platforms: Windows 10

Preconditions

  • Install the Firefox en-CA build
  • Set browser.search.region to CA in about:config
  • Flip following prefs in about:config:
    extensions.formautofill.addresses.capture.v2.enabled = true
    extensions.formautofill.addresses.supported = on
  • Use CA VPN to test

Steps to reproduce

  1. Log into https://www.staples.ca/ , add an item to bag and navigate to checkout page
  2. Fill in the Address Form and press the submit button

Expected result

  • The address doorhanger is triggered upon address form submission.

Actual result

  • The address doorhanger is not triggered upon address form submission.

Regression range

  • Not a recent regression because the feature is disabled by default.

Additional notes

Blocks: 1832508
Severity: -- → S3
Has STR: --- → yes

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

Priority: -- → P3

Note: Autofill module doesn't receive onLocationChange, onStateChange, and onDOMFormRemoved events after clicking the submitting button.

Whiteboard: [fxcm-addr-compatibility]

That the address doorhanger isn't shown isn't wanted behavior but it is "expected".
The reason for this is that the address fields are contained in a cross-origin iframe with the origin staples.boldapps.net. But the navigated window is the top window with the domain checkout.staples.ca. This means the additional form submission listeners were only added for the iframe window because the cross-origin top window is not accessible for it, see getHighestDocShell. Even if we were notified of a page navigation in the top window, the navigation wouldn't affect the iframe window because of it's cross-origin, see isActiveWindowNavigation.

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