Code: Select all
analytics.js:1 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://connect.squareup.com') does not match the recipient window's origin ('null')connect.squareup.com
connect.squareup.com
Since some time, some payment routines in Square Payment Form are writing into an iFrame which is at https://connect.squareup.com/payments/analytics/frame.html (or https://connect.squareupsandbox.com/payments/analytics/frame.html if you are a developer). This iFrame is blocked by a rule in the EasyPrivacy list which blocks everything containing "/analytics/frame.". The result is this error which, since it doesn't even happen in applications' contexts, cannot be handled or worked around:
Can those two URIs be whitelisted?
Please provide a test URL where this can be reproduced.
"If it ain't broke don't fix it."
The links that I'm aware and care about are semi-private (I mean, our users might not be happy that I'm making some of their payment forms googleable, we don't do it). Do you mind if I PM them to you?
In that case I would send them to one of the EasyList authors or
Code: Select all
easylist.subscription @ gmail.com"If it ain't broke don't fix it."
You can reproduce this by going through the purchase flow for a Square Reader. When you get to the payment form, you will see this error in the developer console which is a result from the frame being blocked:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://connect.squareup.com') does not match the recipient window's origin ('null').