Skip to content

perf: trust event-maintained frame tree instead of refreshing per resolution #240

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
suchintan merged 3 commits into from
Aug 15, 2026
Merged

perf: trust event-maintained frame tree instead of refreshing per resolution #240

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7fdb8a0
🔄 synced local 'src/' with remote 'src/'
suchintan Aug 15, 2026
2cfd720
🔄 synced local 'tests/' with remote 'tests/'
suchintan Aug 15, 2026
023ca85
🔄 synced local 'CHANGELOG.md' with remote 'CHANGELOG.md'
suchintan Aug 15, 2026
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: 2 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,11 @@ All notable user-facing changes to Rustwright are documented in this file.

### Changed

- Made frame-tree caching event-maintained: the main page session populates at attachment, OOPIF sessions populate on first locator use and after invalidation, steady-state locators issue no `Page.getFrameTree` calls, and context-bound frame actions retry once during iframe process changes.
- Reduced steady-state object-valued `evaluate()` results to one browser-protocol command after per-realm serializer setup; the first call in a new or recreated realm re-establishes that setup.
- Passive page-error history now records page-authored errors without enabling Chromium's `Runtime` domain; `LIMITATIONS.md` documents the full-detail limitation for evaluate-created asynchronous callbacks.
- Verified support for standard CPython 3.9 through 3.14 and CPython 3.15.0rc1. Python 3.15 support remains pre-release, and CI tracks 3.15-dev until GA.
- Added a public failure and retry contract for browser actions. Rust, Python, and MCP callers can inspect the failure phase, target kind, command-write status, and retry safety. A tracked input command with unknown delivery now raises `UnknownOutcomeError` in Python and is never reported as safe to retry. Other bindings keep their existing error types and receive a clear diagnostic message.
- Browser launch and persistent-context launch now add Chromium's `--use-mock-keychain` and `--password-store=basic` defaults unless callers provide those switches or disable default arguments.

### Fixed

Expand Down
Loading
Loading