1128085 - Boku Continue button doesn't work in a popup

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Payments/Refunds, defect, P4)

Description

[Kumar McMillan [:kumar]]

STR:
- start a payment on the web (such as from desktop Marketplace)
- simulate a Boku-supported network
- when you see the Boku screen, enter a valid number and click Continue to finish the payment.

The Continue button does not redirect back to the Mozilla return URL within the popup. It redirects in the window that opened the popup (probably by looking at window.opener). We need Boku to redirect within the popup window.

Comment 1

[John Tan [Boku Merchant Support]]

Could you please elaborate on what the "Mozilla return URL within the popup" is? 

Normal behavior is that the 'fwdurl' and 'fail-fwdurl' are opened within the same iFrame that housed the Boku payment panel once the "Continue" button is clicked.

Not sure about the exact internal JavaScript workings, but I'd assume that something specific to your display / popup window may be altering the behavior of the Boku 'fwdurl' / 'fail-fwdurl' redirect.

Comment 2

[Kumar McMillan [:kumar]]

Hi John. We have window #1 (the marketplace) that opens window #2 (the payment window) to a Mozilla server. Within the payment window, the user enters their PIN and is redirected to Boku. When I click the Continue button to complete the Boku purchase, I see the payment window get closed automatically (or maybe hidden) and the Mozilla return URL (the fwdurl) is loaded within window #1, the marketplace. I'm not sure exactly why yet but it seems like the JavaScript handler on Boku's Continue button is maybe closing the window or maybe it's just looking at window.opener (which is the marketplace) for security reasons (?) and loading the fwdurl there.

Comment 3

[John Tan [Boku Merchant Support]]

I'm fairly certain that our payment panel's "Continue" behavior was designed with security / compatibility as primary considerations, as its implementation is used without issue on both Android embedded browser instances and our desktop payment panel. While I'm not certain of the the Firefox OS marketplace window configuration, it seems that there should be some way to direct the payment panel to treat window #2 as the window.opener?