634453 - paypal JS errors when requesting a page via Selenium

Status: RESOLVED INVALID

(addons.mozilla.org Graveyard :: Public Pages, defect, P5)

Description

[Vishal Kamdar [:vish_moz]]

1. Automation tool Selenium uses a proxy server.
2. When automation test gets on this page https://addons.allizom.org/en-US/firefox/personas/ you get Java Script errors such as:

Error: PAYPAL is undefined
Source File: https://addons-cdn.allizom.org/media/js/common-min.js?build=6692005
Line: 49

Error: Permission denied for <https://addons.allizom.org> to get property Window.dgFlow from <>.
Source File: https://addons-cdn.allizom.org/media/js/common-min.js?build=6692005
Line: 49

Comment 1

[Andy McKay]

The paypal is now lazier loading so should only trigger if you are testing contributions. If you do test contributions, I would expect problems.

Comment 2

[Vishal Kamdar [:vish_moz]]

Still seeing the JS errors even when not testing contributions (only via Selenium). This page is one of them:
https://addons.allizom.org/en-US/firefox/personas/

As a result, you don't see the arrows on the carousel.

Comment 3

[Andy McKay]

I don't get any errors and after my change yesterday, paypal isn't loaded at all on that page. Is the selenium setup documented somewhere so I can duplicate here?

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #3)
> I don't get any errors and after my change yesterday, paypal isn't loaded at
> all on that page. Is the selenium setup documented somewhere so I can duplicate
> here?

The PayPal error is now gone, but we're still seeing the other error:

Error: Permission denied for <https://addons.allizom.org> to get property
Window.dgFlow from <>.
Source File:
https://addons-cdn.allizom.org/media/js/common-min.js?build=6692005
Line: 49

Looks like some bizarre interaction with jQuery + Selenium's proxy setup...

Comment 5

[David Burns :automatedtester]

It looks like Selenium *may* be suffering from Same Origin Policy. I would try with *chrome instead of *firefox

Comment 6

[Vishal Kamdar [:vish_moz]]

Yes, using *chrome which launches Firefox browser in a lesser secure mode works.
So it was the issue with Selenium's Same Origin Policy.
Marking the bug as Invalid.