Skip to content

Update browser-rendering.yaml #24101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 4, 2025
Merged

Update browser-rendering.yaml #24101

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a6e655f
Update browser-rendering.yaml
kathayl Jul 31, 2025
70e1568
Update screenshot-endpoint.mdx
kathayl Jul 31, 2025
e9ac876
Update src/content/release-notes/browser-rendering.yaml
kathayl Aug 1, 2025
b9a55f9
Apply suggestions from code review
ToriLindsay Aug 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/content/docs/browser-rendering/rest-api/screenshot-endpoint.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,9 @@ For more options to control the final screenshot, like `clip`, `captureBeyondVie

:::note
Copy link
Contributor

@ToriLindsay ToriLindsay Aug 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A thought on this one...
I tend to assume that one note = one concept. In this case, am I right in understanding that these two pieces of information are unrelated to each other (except for the fact that they are both good things to know for basic usage)? If so, I would suggest either:

  • Keep as a note, but put a heading on the note like Notes for basic usage and then bullet each, to make it obvious that they may be unrelated concepts.
  • Break into two separate notes and maybe give them both headings. (I'm not partial to this because it's a little too busy. And it's also hard to scale if we end up with more notes).
  • Make into a bulleted list of "Additional things to know..." but don't use the note component at all.

The `quality` parameter is not compatible with the default `.png` format and will return a 400 error. If you set `quality`, you must also set `type` to `.jpeg` or another supported format.

By default, the browser viewport is set to **1920×1080**. You can override the default via request options.

:::

## Advanced usage
Expand Down
2 changes: 1 addition & 1 deletion src/content/release-notes/browser-rendering.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ entries:
* Local development with `npx wrangler dev` now supports [Playwright](/browser-rendering/platform/playwright/) when using Browser Rendering. Upgrade to the latest version of wrangler to get started.
* The [`/content` endpoint](/browser-rendering/rest-api/content-endpoint/) now returns the page's title, making it easier to identify pages.
* The [`/json` endpoint](/browser-rendering/rest-api/json-endpoint/) now allows you to specify your own AI model for the extraction, using the `custom_ai` parameter.
* The default viewport size has been increased from 800x600 to 1920x1080. You can still override the viewport via request options.
* The default viewport size on the [`/screenshot` endpoint](/browser-rendering/rest-api/screenshot-endpoint/) has been increased from 800x600 to 1920x1080. You can still override the viewport via request options.
- publish_date: "2025-07-25"
title: "@cloudflare/puppeteer 1.0.4 released"
description: |-
Expand Down