openclaw - ✅(Solved) Fix Browser screenshot fails on Chrome 146+ with managed browser (fromSurface: false) [1 pull requests, 1 comments, 2 participants]

openclaw2026-04-03 21:11:24

ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#60540•Fetched 2026-04-08 02:49:53

View on GitHub

Comments

Participants

Timeline

Reactions

Author

abhione

Participants

abhione

mvanhorn

Timeline (top)

closed ×1commented ×1cross-referenced ×1locked ×1

Root Cause

In routes-GmL6Gsmc.js, the captureScreenshot function (line ~4959) uses:

const base64 = (await send('Page.captureScreenshot', {
    format,
    fromSurface: false,  // <-- THIS
    captureBeyondViewport: true
}))?.data;

fromSurface: false tells Chrome to capture from the compositor surface rather than the rendered surface. On Chrome 146+ with a managed/headful browser that isn't in the foreground, the compositor doesn't have rendered content available, so the screenshot returns empty/null data.

Code Example

const base64 = (await send('Page.captureScreenshot', {
    format,
    fromSurface: false,  // <-- THIS
    captureBeyondViewport: true
}))?.data;

RAW_BUFFERClick to expand / collapse

Bug Report

OpenClaw version: Latest (installed via homebrew) Chrome version: 146.0.7680.178 macOS: Darwin 25.3.0 (arm64)

Problem

browser screenshot consistently returns Unable to capture screenshot for the managed browser (openclaw profile), while browser snapshot works perfectly. All other browser actions (click, type, navigate, open) work fine.

Root Cause

In routes-GmL6Gsmc.js, the captureScreenshot function (line ~4959) uses:

const base64 = (await send('Page.captureScreenshot', {
    format,
    fromSurface: false,  // <-- THIS
    captureBeyondViewport: true
}))?.data;

Evidence

Direct Playwright page.screenshot() (which defaults to fromSurface: true) works perfectly on the same page/target
CDP Page.captureScreenshot with fromSurface: true (or omitted) succeeds
The issue reproduces consistently regardless of which page is loaded
Snapshots (DOM accessibility tree) always work since they don't depend on rendering

Suggested Fix

Change fromSurface: false to fromSurface: true (or remove the parameter entirely to use Chrome's default of true).

Workaround

Use browser snapshot instead of browser screenshot for all automation tasks. Snapshots provide the DOM tree which is sufficient for click/type/navigate automation.

extent analysis

TL;DR

Change the fromSurface parameter to true in the captureScreenshot function to fix the screenshot issue.

Guidance

Verify that the issue is specific to Chrome version 146+ and managed/headful browsers not in the foreground.
Check the captureScreenshot function in routes-GmL6Gsmc.js to confirm the fromSurface parameter is set to false.
Update the captureScreenshot function to use fromSurface: true or remove the parameter to use Chrome's default.
Test the fix by running the browser screenshot command with the updated captureScreenshot function.

Example

const base64 = (await send('Page.captureScreenshot', {
    format,
    fromSurface: true,  // Update this line
    captureBeyondViewport: true
}))?.data;

Notes

This fix assumes that the issue is caused by the fromSurface parameter being set to false in the captureScreenshot function. If the issue persists after updating the function, further investigation may be needed.

Recommendation

Apply the suggested fix by updating the fromSurface parameter to true to resolve the screenshot issue, as this change is specific to the identified root cause and does not introduce additional dependencies or version upgrades.

Vote matrix · Quick signals

Works

Did the solution work? Tap to confirm.

Easy Fix

Was it a quick fix?

Time Saver

Did it save you time?

Blocking

Was it severely blocking?

Common Issue

Are others likely hitting this too?

Flaky / Intermittent

Is it intermittent?

Verified / Reproducible

Can you reproduce it reliably?

#inference speed #output truncation #response parsing #generation error #database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

openclaw - ✅(Solved) Fix Browser screenshot fails on Chrome 146+ with managed browser (fromSurface: false) [1 pull requests, 1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Root Cause

Fix Action

Workaround

PR fix notes

PR #60682: fix(browser): remove fromSurface: false for Chrome 146+ screenshot compat

Description (problem / solution / changelog)

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Root Cause (if applicable)

Regression Test Plan (if applicable)

Changed files

Code Example

Bug Report

Problem

Root Cause

Evidence

Suggested Fix

Workaround

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

RELATED_DISCOVERY

TRENDING