workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
🤖turnstile
radar
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
pipelines-beta
containers-beta
I'm building a webperf tester (e.g. say
I'm building a webperf tester (e.g. say similar to PageSpeed Insights) but on top of CF Puppeteer. I saw turnstile/bot challenges on some Cloudflare zones, but I'm surprised that Cloudflare's Radar itself also does get challenged.
I guess this is bot traffic so it makes sense. Would the expected behavior be that any domains who aggressively block bots should allow explicitly (via custom header or user-agent)? Or if you hit enough traffic (+1k requests/day) apply to be a verified bot?...
Hello everyone! We've got a pipeline
Hello everyone! We've got a pipeline working where screenshots are taken of specific routes in our app that we want to use for generating thumbnail previews of pages — however when the pages contain CSS filters on images (right side of the browser window) the filters are not applied. Additionally, when we use backdrop filter blur on a content area (left side of the browser window) the backdrop blur is rendered but the content of the div is not.
The attached screenshot is a preview of the Cloudflare Browser Rendering API result positioned over top of the actual page that was being screenshot in the browser.
Is there anything we can do from our side to better troubleshoot this? We've done everything we can as far as vendor prefixing to make the effects as backwards compatible as possible. Are we hitting limits of the Browser Rendering API or are there ways to work around the issue?...
Cloudflare's Pupeteer Browser Rendering
Cloudflare'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/...
