Hi, I am hoping to get access to the Puppeteer Browser Rendering for some personal use case (dynamic
Hi, I am hoping to get access to the Puppeteer Browser Rendering for some personal use case (dynamic resume.pdf generation) on my personal site.
Cit's available to everyone on Workers Paid now
https://blog.cloudflare.com/browser-rendering-api-ga-rolling-out-cloudflare-snippets-swr-and-bringing-workers-for-platforms-to-our-paygo-plans
https://blog.cloudflare.com/browser-rendering-api-ga-rolling-out-cloudflare-snippets-swr-and-bringing-workers-for-platforms-to-our-paygo-plans
Acould you share the code?
JI'll see if I can get permission to share anything. I know I won't be able to share the whole repo because it's not a standalone repo, but I might be able to extract some relevant parts like the docker file and controller code
AYeah. That would be great. Just de docker and kubernets setup.
WPhew that's been a little hard to track down how I get access to it!
AHello 
Excuse me if I misunderstood, Is it here where we ask for access to the browser rendering Api?
Thanks!
Excuse me if I misunderstood, Is it here where we ask for access to the browser rendering Api?
Thanks!
UYou dont have to ask, browser rendering is a publicly available product. You just need the workers paid plan
ASweet thank you very much!
WYeah you need Workers Paid for browser bindings
WI should improve that error message and return a "no_workers_paid" error
A@Walshy | Deploying
I?pings
FPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
Acompatibility_date = "2023-03-14"
node_compat = true
thats the fix
node_compat = true
thats the fix
MHi! I'm also new to the browser rendering API (and new to workers too... excited to be here!) If I upgrade to a paid workers account should the browser rendering work with the tutorial provided?
A@sc Hello, I found that the type in the code is not quite right and I have submitted a pull request, could you review it? https://github.com/cloudflare/puppeteer/pull/44
GitHub
What kind of change does this PR introduce?
fix type
Did you add tests for your changes?
no need
If relevant, did you update the documentation?
no need
Summary
fix type
Does this PR introduce a ...
fix type
Did you add tests for your changes?
no need
If relevant, did you update the documentation?
no need
Summary
fix type
Does this PR introduce a ...
CDoes cloudflare browser rendering support aspx pages? I'm getting a
__doPostBack is not defined error when running puppeteer in browser rendering. I tried the same code in local puppeteer on node, and it works just fine. The page loads fine on both, a screenshot of the page looks the same on both. I also used puppeteer verison 17 locally, since that's the version that @cloudflare/puppeteer is forked from. Still not working. Any thoughts?CWould appreciate any help here. Tried a bunch of different methods in cloudflare puppeteer before realizing it works perfectly fine in a local puppeteer.
IThis most likely means there aren't any components on the page that can trigger a postback. https://stackoverflow.com/a/3480384/46914
Stack Overflow
Im getting that error when try to call a doPostBack on one of my pages, every page that i have in the project use doPostBack function but in this particular page im getting that Javascript erro...
I@Conner If there are components, then this could be a race condition. try adding a wait to your puppeteer script.
CAwesome thanks... what should I wait for?
Because I screenshot the page before doing __doPostBack and everything looks loaded in
Because I screenshot the page before doing __doPostBack and everything looks loaded in
Ithere might be a "scripts loaded" event in puppeteer, or maybe you need to turn on JS support. not 100% sure.
I@Conner You could use
Page.waitForFunction() to return a truthy value https://pptr.dev/api/puppeteer.page.waitforfunctionWaits for the provided function, pageFunction, to return a truthy value when evaluated in the page's context.
CI'm evaling other code before that to be clear
Basic querySelector for elements on the page
Basic querySelector for elements on the page
CJust seems to be that function that's not available
Ithe elements will exist on thet page from the start since they're rendered on the server, however, the JS that adds
__doPostBack will not be instantaneous.CAh that makes sense
CI'll try a waitForFunction thanks
Iyou could also just try a 5 second timeout to see if that works since it will confirm it's a race condition.
Iit most likely works locally because the page network response times are faster locally.
Iwait, did you try locally but pointing at the remote page?
CYes locally pointing at the remote page
CSame code locally and in cloudflare, a remote site I'm scraping
Iokay.
IEnsure you have
waitUntilloadCI do yeah
I'll try the waitForFunction gimme a couple minutes and I'll lyk
I'll try the waitForFunction gimme a couple minutes and I'll lyk
Cawait page.waitForFunction(() => typeof window.__doPostBack === 'function');Ihttps://www.webshare.io/academy-article/puppeteer-wait-for-page-to-load this article explains the various waitUntil options. You can wait for network idle, for example.
CI do have
networkidle0 actually yeahC@Ian The waitForFunction didn't work,
TimeoutError: waiting for function failed: timeout 30000ms exceededCAny chance cloudflare's browser might not load the aspx?
Iokay, so the JS is never running.
Inothing about ASPX pages that make them special.
IIt could be a config difference.
