Adding those two preferences in about:config suppressed the "TypeError: G is not a function" errors but had no noticeable effect on the behaviour of the web page; the console log reported:
TypeError: l is not a function rs=A... :3440:202
TypeError: l is not a function rs=A... :2746:91
TypeError: l is not a function rs=A... :3440:202
TypeError: l is not a function rs=A... :5594:388
TypeError: l is not a function rs=A... :3440:202
Thanks for reporting back. Seeing that different people's console messages say completely different things regarding 'l' (one set of console messages indicates that l is expected to be a window? and yours expects a function) I think that's all the help I can give (at least for the moment), so I'll leave this thread alone now.
*Always* check the changelogs BEFORE updating that important software!
Guest wrote:I am the OP and if I understand your answer we will not receive a solution for this behavior of NoScript?
Nope - I'm not the dev, Giorgio Maone is; and besides, it's not that we don't want to solve it, it's that the myriad reports of this issue are too different for us to be able to investigate anything ourselves. I wanted to leave this thread alone at least for the time being, because all I can see to do atm is wait for a reasonably techie user of Google Play to be able to A) reproduce the problem, B) explain why different users get such drastically different symptoms, and C) know how to dig around in the site's JS enough that they can either create/fix a surrogate themselves or collaborate with us for surrogate.
Guest wrote:Nevertheless many thanks for your work!
You're welcome.
*Always* check the changelogs BEFORE updating that important software!
to those who whitelisted google-analytics.com and it didn't fix anything, by any chance were you running an adblock-type extension? try disabling that and with google-analytics.com blacklisted, see if it works.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0