Skip to content

Add kiosk mode as first viewport recommendation - #491

Merged
ehfeng merged 4 commits into
mainfrom
hypeship/add-kiosk-mode-viewport
Aug 7, 2026
Merged

Add kiosk mode as first viewport recommendation#491
ehfeng merged 4 commits into
mainfrom
hypeship/add-kiosk-mode-viewport

Conversation

@ehfeng

@ehfeng ehfeng commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Adds kiosk mode (--kiosk flag) as the first recommendation in the "Window size vs. page viewport" section. Kiosk mode removes Chromium's browser UI so the window dimensions match the page viewport exactly, which is the simplest way to solve the mismatch problem.


Note

Low Risk
Documentation-only edits to viewport guidance; no runtime, API, or security behavior changes.

Overview
Updates browsers/viewport.mdx so kiosk mode is the first fix when window size and page viewport must match on headful browsers.

The new bullet explains that kiosk_mode: true hides Chromium UI so configured viewport dimensions align with the rendered page, with TypeScript and Python browsers.create examples combining kiosk_mode and viewport.

The automation-framework option is reworded to call out that setViewportSize / set_viewport_size change the rendered page but do not update live view or computer controls.

Reviewed by Cursor Bugbot for commit 8b27c2f. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Aug 7, 2026, 12:52 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@vercel

vercel Bot commented Aug 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Error Error Aug 7, 2026 1:02am

cursor[bot]
cursor Bot approved these changes Aug 7, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Stale comment

Risk assessment: Very Low

Verdict: Risk remains Very Low after the synchronize update. Existing approval retained (not re-approved; risk did not increase).

Re-evaluation context

  • Prior automation approval was on 0bc296e (launch_args: ["--kiosk"]).
  • Head is now a0389e7, which only swaps the docs examples to kiosk_mode: true / kiosk_mode=True.
  • That follow-up is still documentation-only and does not raise risk, so approval is not revoked.

Evidence (from current diff only)

  • 1 file changed: browsers/viewport.mdx (+20 / −0 vs base)
  • Change type: Documentation-only — adds a kiosk-mode recommendation and TypeScript/Python examples under the existing "Window size vs. page viewport" section
  • No application/runtime code, infra, auth, schema, config, or shared-library changes
  • No CODEOWNERS file requiring a separate ownership review
  • Not an LLM/system-prompt instruction change (product docs page)

Risk factors

Factor Assessment
Codepaths modified Docs page only
Blast radius None (no executable product logic)
Complexity Low — additive prose + examples
Infrastructure impact None
User-facing surface Docs content only
Operational / security risk None identified

Decision

Very Low → leave prior approval in place; comment-only re-assessment per automation policy (do not re-approve).

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Stale comment

Risk assessment: Very Low

Verdict: Risk remains Very Low after this synchronize update. Existing approval retained (not re-approved; risk did not increase).

Re-evaluation context

  • Prior automation approval was on an earlier commit; head is now 8ab649d.
  • Diff vs main is still a single documentation file with additive guidance and examples.
  • Latest commits only adjust docs example parameters / wording (kiosk_mode, remove redundant SDK param mention). That does not raise risk, so approval is not revoked.

Evidence (from current diff only)

  • 1 file changed: browsers/viewport.mdx (+20 / −0)
  • Change type: Documentation-only — adds a kiosk-mode recommendation and TypeScript/Python examples under the existing "Window size vs. page viewport" section
  • No application/runtime code, infra, auth, schema, config, or shared-library changes
  • No CODEOWNERS file requiring a separate ownership review
  • Not an LLM/system-prompt instruction change (product docs page)

Risk factors

Factor Assessment
Codepaths modified Docs page only
Blast radius None (no executable product logic)
Complexity Low — additive prose + examples
Infrastructure impact None
User-facing surface Docs content only
Operational / security risk None identified

Decision

Very Low → leave prior approval in place; comment-only re-assessment per automation policy (do not re-approve).

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@ehfeng
ehfeng marked this pull request as ready for review August 7, 2026 01:03
@ehfeng
ehfeng merged commit 796a23e into main Aug 7, 2026
6 of 7 checks passed
@ehfeng
ehfeng deleted the hypeship/add-kiosk-mode-viewport branch August 7, 2026 01:03

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Stale comment

Risk assessment: Very Low

Verdict: Risk remains Very Low after this synchronize update. Existing approval retained (not re-approved; risk did not increase).

Re-evaluation context

  • Prior automation approval exists on an earlier commit; head is now 8b27c2f.
  • Diff vs base is still a single documentation file with additive guidance and examples.
  • Latest commit only clarifies that the automation-framework viewport option updates rendered page size but is not reflected in live view / computer controls. That does not raise risk, so approval is not revoked.

Evidence (from current diff only)

  • 1 file changed: browsers/viewport.mdx (+21 / −1)
  • Change type: Documentation-only — adds a kiosk-mode recommendation with TypeScript/Python examples, and rewords the existing automation-framework bullet
  • No application/runtime code, infra, auth, schema, config, or shared-library changes
  • No CODEOWNERS file requiring a separate ownership review
  • Not an LLM/system-prompt instruction change (product docs page)

Risk factors

Factor Assessment
Codepaths modified Docs page only
Blast radius None (no executable product logic)
Complexity Low — additive prose + examples
Infrastructure impact None
User-facing surface Docs content only
Operational / security risk None identified

Decision

Very Low → leave prior approval in place; comment-only re-assessment per automation policy (do not re-approve).

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Risk assessment: Very Low

Verdict: Risk remains Very Low after this update. Existing approval retained (not re-approved; risk did not increase).

Re-evaluation context

  • Prior automation approval exists on an earlier commit; head is 8b27c2f.
  • Diff vs base is still a single documentation file with additive guidance and examples.
  • Latest change only adds a kiosk-mode recommendation (with TypeScript/Python examples) and clarifies that the automation-framework viewport option updates rendered page size but is not reflected in live view / computer controls. That does not raise risk, so approval is not revoked.

Evidence (from current diff only)

  • 1 file changed: browsers/viewport.mdx (+21 / −1)
  • Change type: Documentation-only — adds a kiosk-mode recommendation with TypeScript/Python examples, and rewords the existing automation-framework bullet
  • No application/runtime code, infra, auth, schema, config, or shared-library changes
  • No CODEOWNERS file requiring a separate ownership review
  • Not an LLM/system-prompt instruction change (product docs page)

Risk factors

Factor Assessment
Codepaths modified Docs page only
Blast radius None (no executable product logic)
Complexity Low — additive prose + examples
Infrastructure impact None
User-facing surface Docs content only
Operational / security risk None identified

Decision

Very Low → leave prior approval in place; comment-only re-assessment per automation policy (do not re-approve).

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 8b27c2f. Configure here.

Comment thread browsers/viewport.mdx
)
```

</CodeGroup>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Duplicates kiosk create walkthrough

Low Severity

The new kiosk CodeGroup repeats the create-browser walkthrough already documented on the Live View kiosk page instead of giving context-specific viewport guidance and linking to that canonical section.

Fix in Cursor Fix in Web

Triggered by learned rule: Single source of truth — no deep content duplication across pages

Reviewed by Cursor Bugbot for commit 8b27c2f. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant