Skip to content

Conversation

@dprevoznik
Copy link
Contributor

@dprevoznik dprevoznik commented Sep 24, 2025

Description

Updating the browser_session definition to reflect viewport handling changes in recent versions of browser-use (<0.7.0). The BrowserSessionCustomResize workaround is no longer required in the latest release. It remains available for users who choose to run older versions of browser-use, where custom resizing is still necessary.

Implementation Checklist

  • Implemented this change in TypeScript
  • Implemented this change in Python

Docs

  • [n/a] Link to a PR in our docs repo documenting your change (if applicable)

Visual Proof

Updated an example repo to match the uvlock + code snippet set up and confirm it was working still.

Related Issue

Fixes x.com comment left by a User.


TL;DR

Removes the BrowserSessionCustomResize workaround from the Python browser-use template, as it's no longer required for recent versions of the browser-use package.

Why we made these changes

Recent versions of the browser-use package (>=0.7.0) handle viewport resizing automatically, making our custom workaround obsolete. This change simplifies the template for users on the latest version and addresses user feedback. The workaround remains available for users running older versions.

What changed?

  • Updated the browser_session definition in the Python browser-use template to remove the custom viewport resizing logic.
  • The BrowserSessionCustomResize class is no longer necessary for the default setup, simplifying the template's code.

Description generated by Mesa. Update settings

Updating the browser_session definition to reflect viewport handling changes in recent versions of browser-use. The BrowserSessionCustomResize workaround is no longer required in the latest release. It remains available for users who choose to run older versions of browser-use, where custom resizing is still necessary.
Copy link

@mesa-dot-dev mesa-dot-dev bot left a comment

Choose a reason for hiding this comment

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

Performed full review of 0f6b521...8a6817c

Analysis

  1. The version constraint >=0.7.0 has no upper bound, which could expose the system to breaking changes in future major versions of browser-use.

  2. Hardcoded browser dimensions (1024x786) in the new implementation may limit flexibility for different use cases that require varying viewport sizes.

  3. While modernizing the API usage is positive, the migration from a custom solution to the native Browser configuration might have edge cases not covered by the current testing.

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

Slash Commands:

  • /review - Request a full code review
  • /review latest - Review only changes since the last review
  • /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
  • /help - Get help with Mesa commands and configuration options

3 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings

Copy link
Contributor

@juecd juecd left a comment

Choose a reason for hiding this comment

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

LGTM, thank you!

@dprevoznik dprevoznik merged commit 4ff2867 into main Sep 24, 2025
7 checks passed
@dprevoznik dprevoznik deleted the KERNEL-358 branch September 24, 2025 19:43
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.

4 participants