#peter-belbin_unexpected

1 messages · Page 1 of 1 (latest)

midnight pantherBOT
#

👋 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/1273027324937502781

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

visual kilnBOT
#

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.

sharp bane
#

Hi there

rancid ledge
#

hey

sharp bane
#

Ah, I think we've chatted about UI testing before 🙂

rancid ledge
#

Also tried using the Payment Element, and this made absolutely no difference in terms of whether the responses were received or not.

rancid ledge
sharp bane
#

I don't think I'll be able to help here. I recommend working with Storybook on this. If I understand this correctly, the CardElement (and PaymentElement) are rendering as expected but it's the tool you're using on top of these that's failing to take a screenshot of what's displayed in the browser?

rancid ledge
#

no. this is not correct.

#

For a long time, we've been able to capture the rendered Stripe elements on our web pages.

sharp bane
#

What do you mean by capture exactly?

rancid ledge
#

by 'capture', I mean: get a png image of a webpage that happens to have some portion of it that has the Card Element in it. That's what storycap does.

#

Storybook is a web server tooling that generates a website having various particular scenarios represented. If I start Storybook and use the website manually, the pages render with the Card Element just fine.

#

However, to automate that process, something called storycap is used to remote-control a browser to visit each of the storybook website 'story' pages, and capture each as a PNG image.

#

storycap uses puppeteer to remote-control a browser instance.

#

So, when this capture process is running is when we're finding, as I say, only recently, that there appear now to be issues of the browser sometimes not receiving a response to the request for one or more Stripe web requests. Of course, since the browser taking the screenshot has to wait for all content to be available, it's gumming up the works.

sharp bane
#

Is there any sort of delay you can introduce on the storycap side?

rancid ledge
#

Have you given the sample GitHub project a try to see it happening for yourself?

sharp bane
#

No, I'm not going to run this since the issue seems to lie outside of Stripe

rancid ledge
#

Well, you know, I was asked by people from Stripe to provide a minimal reproduction that demonstrates the issue so that it could be looked at. And you're now telling me that you aren't going to look at it. What the what???

#

ie: if you go and look at some of the other threads, you'll find that I was asked to produce a minimal reproduction of the problem.

sharp bane
#

We're not goint to test storycap functionality, though

rancid ledge
#

The project also has the starting of a storybook server that hosts a simple test story, which is what's also able to be accessed using a normal browser.