[CA][www.staples.ca] The Address Doorhanger is not displayed upon address form submission
Categories
(Toolkit :: Form Autofill, task, P3)
Tracking
()
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
- Log into https://www.staples.ca/ , add an item to bag and navigate to checkout page
- 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
- The address doorhanger is triggered in Google Chrome, although the wrong country is captured.
- Fathom Fox page: https://drive.google.com/file/d/17Uu8FCuR3ewSEoMTcnQshviDu9LlZO2V/view?usp=sharing
Reporter | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
:epopescu, if you think that's a regression, could you try to find a regression range using for example mozregression?
Updated•1 year ago
|
Comment 2•8 months ago
|
||
Note: Autofill module doesn't receive onLocationChange
, onStateChange
, and onDOMFormRemoved
events after clicking the submitting button.
Updated•7 months ago
|
Updated•7 months ago
|
Comment 3•7 months ago
|
||
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.
Description
•