mirror of https://github.com/remorses/playwriter.git synced 2026-09-14 16:37:40 +08:00

Files

T

Tommy D. Rossi bd6c7eb363 fix playwriter multi-profile browser routing

Route extension relay connections by their per-profile install id before falling back to Google account identity. This keeps two Chrome profiles signed into the same account from replacing each other in the relay.

Keep Playwright-created tabs in the intended Chrome window by remembering the window where the extension was activated and using that window for Target.createTarget and initial tabs.

Handle Chrome debugger cancellation as a global detach event. When Chrome reports canceled_by_user, clear all tracked debugger tabs and emit detach events so Playwright stops sending commands to tabs Chrome already detached from. Also avoid resurrecting stale error tab state if the detach happens while attachTab is still unwinding.

Validation:
- pnpm test --run src/relay-state.test.ts
- pnpm typecheck
- pnpm build in extension/
- Manual two-profile Hacker News navigation and comment extraction
- Mythos review found no blocking issues

Session: ses_120923e0fffe5l4GT77WwyXEGP

2026-06-19 13:31:31 +02:00

fix-profile-relay-selection.md

fix playwriter multi-profile browser routing

2026-06-19 13:31:31 +02:00

readme.md

docs: document changesets workflow for agents

2026-05-09 08:38:06 +02:00

readme.md

Changesets

This folder contains pending release notes for public packages. Each .md file describes one user-facing fix or feature that should appear in the next generated changelog.

What to put here

Add one descriptive kebab-case .md file per logical change, for example fix-auth-token-refresh.md.
Use patch for fixes and minor for new features.
Write in present tense, focused on what users see.
Check GitHub issues first. If the change fixes one, include Fixes #123 on its own line.

What not to put here

Do not add changesets for private packages or packages without a version field.
Do not edit CHANGELOG.md directly.
Do not run the interactive changeset CLI.
Do not add vague entries like "misc improvements" or "update internals".