so the 2 new browser per minutes is not an issue, but i have not enough experience with workers to t
so the 2 new browser per minutes is not an issue, but i have not enough experience with workers to tell if that's the case
Swell for my use case needed anonymity , need to change browser fingerprint , that can be only be done with reopening browser .
Syou dont want to deal with cdp remote debugging , it uses websockets and so pain in the ass
VIf end time, closed reason is empty...Does that mean the browser still running? If yes, I thought there was a maximum 2 browser limit per account. So, how I can see 10-15 browser are running as I don't see
Close reason on many on dashboard.
VSounds like Cloudflare team needs to address this, let's wait for the morning if someone comment here from CF.
VThanks for update.
Shave you got any answers ?
AExtra wont work. As it extends puppeteer just like cf does. One would need to modify it for cf
SForking time
SBrowser Rendering Test Feature for Free workers when
M+1
JNope, never got any support from anyone. Actually implemented my own puppeteer worker inside my kubernetes cluster and I've used it successfully thousands of times since I posted this. It was a waste of time to try the browser. Rendering in cloudflare, wasted an entire day of my developer time. Especially since nobody could support the bugs that were there.
JCloudflare's Pupeteer Browser Rendering worker example does not show sticky navs for some reason--both for my website and others I've tried like Shadcn's site.
Any ideas how to make the sticky nav visible in the screenshot, like it is when visiting the website in a regular brower?
I've tried every setting I can think of, delays, etc. My code is based on the basic example: https://developers.cloudflare.com/browser-rendering/get-started/screenshots/
Any ideas how to make the sticky nav visible in the screenshot, like it is when visiting the website in a regular brower?
I've tried every setting I can think of, delays, etc. My code is based on the basic example: https://developers.cloudflare.com/browser-rendering/get-started/screenshots/
JHi, 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.