#davidgs_error
eager mistBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1225869034441146409
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cosmic wrenBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- davidgs_api, 1 day ago, 29 messages
pine bear
Hi 👋
Can you describe your integration? What specific Stripe products are you integrating and how?
spice dust
I have a Stripe embedded payment page. Anytime the local page loads, I get one of those, and whenever I click a 'Buy' button that takes me to Stripe, I get dozens of them
Also getting this:
js?key=AIzaSyCuvGvOqj_eSUVyAu3Dwq47JBdpAN3r-5Y&libraries=places&callback=initGoogleMapsService:288 Google Maps JavaScript API has been loaded directly without loading=async. This can result in suboptimal performance. For best-practice loading patterns please see https://goo.gle/js-api-loading
When you say "Stripe embedded payment page" are you referring to Stripe Checkout? Pricing Table?
spice dust
So I get one when I load a Stripe Pricing Table on my site. When somone clicks to buy, I see dozens of them on rthe Checkout page.
That's the log from ONE load.
spice dust
I have a pricing table on MY site. That takes you to a checkout page on checkout.stripe.com
pine bear
Right, I was asking what you have on your site.
So, the errors you are seeing in the console, these only occur after a customer has left your site?
spice dust
The Pricing Table only throws the one cross-origin error. Once they get to the checkout page, it's a river of them.
As well as the google maps api error, and 7 or 8 of these '/c/pay/cs_test_a1V6DOXYSnvQmOLWGRO70fXbMGPm3xAyDkkEnwKTxpqkSL3bkFNRuHV1Fx#fidkdWxOYHwnPyd1blpxYHZxWjA0SlxAYG9CcE5UfVNVZHZRaExVNVx1XGwzZ0hmMFx9VWFnUUpBTjNDSjV0cFQ8ZmlcZ3c8UUY8TmxtczZqN39TPUB3R1w3fVdBMUpya0lLan1iQDczMEczNTV8dHwyYEFuSyd4JSUl:1 Third-party cookie will be blocked. Learn more in the Issues tab.'
pine bear
Do any of these impact the Checkout flow?
spice dust
Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, setting third-party cookies will be blocked. This behavior protects user data from cross-site tracking.
Please refer to the article linked to learn more about preparing your site to avoid potential breakage.
1 cookie
Name Domain & Path
m m.stripe.com/
1 request
6
Not yet, as far as I can tell. It just looks horrible if anyone looks at the console, and I'm worried that at some point, things will stop working because of them.
I work very hard to keep the console clean in case folks look.
pine bear
But at that point there isn't anything you control. The customer has been redirected to a surface entirely owned by Stripe
spice dust
True. So why is Stripe polluting the console with all these errors?
Seems like a bug to me.