f793dd8ac4
This commit batches the pending workspace updates that were coupled in practice: extension reliability fixes, ghost cursor persistence across MPA navigations, timeout tuning, and aligned docs/versioning updates so behavior and guidance stay in sync. Key updates:\n- extension: add MV3 keepalive via chrome.alarms, add alarms permission, and bump extension changelog/version to 0.0.73 to reduce silent relay disconnects while idle\n- playwriter runtime: raise default action timeout to 60s while keeping navigation timeout separate; increase relay /version fetch timeout to 2000ms\n- recording + cursor: add persistent cursor init scripts with Page.addScriptToEvaluateOnNewDocument, remove init script on teardown, and ensure cursor enablement before applying mouse actions\n- demo video defaults: use 0.5s side buffer (1s total) and default idle speed 6x for createDemoVideo/computeIdleSections\n- tests/docs: keep click-error tests deterministic with explicit 5000ms per-click timeout, remove outdated click-timeout section from skill mistakes, and update package/changelog entries
2.3 KiB
2.3 KiB
Changelog
0.0.73
Bug Fixes
- Service worker keepalive via chrome.alarms: Added
chrome.alarmskeepalive to prevent Chrome MV3 from terminating the service worker when idle. Without this, themaintainLoopstops, the WebSocket closes, and the extension silently disconnects from the relay server — causingsession newto fail with "Extension did not connect within timeout."
0.0.72
Bug Fixes
- Use runtime-scoped root CDP tab session IDs: Root tab sessions now use
pw-tab-<scope>-<n>instead ofpw-tab-<n>, where scope is a random value generated once per extension runtime. This prevents session ID collisions across multiple connected Chrome profiles.
0.0.71
Bug Fixes
- Route Runtime.enable to child CDP sessions: Runtime enable/disable now uses the incoming
sessionIdwhen targeting OOPIF child sessions instead of always using the tab root session. This fixes missingRuntime.executionContextCreatedevents for child iframe targets, which could cause iframe locator operations to hang.
0.0.69
Features
- First extension keeps connection: When multiple Playwriter extensions are installed, the actively-used one (with tabs) now keeps the connection. New extensions are rejected with code 4002 instead of taking over.
- Smarter reconnection: Extension now polls
/extension/statusforactiveTargetscount and only attempts reconnection when the other extension has no active tabs.
Bug Fixes
- Proper state handling for 4002 rejection: Fixed issue where extension would keep retrying forever when rejected during WebSocket handshake. Now correctly enters
extension-replacedpolling state.
0.0.68
Bug Fixes
- Improved connection reliability: Use
127.0.0.1instead oflocalhostto avoid DNS/IPv6 resolution issues - Global connection timeout: Added 15-second global timeout wrapper around
connect()to prevent hanging forever when individual timeouts fail - Better WebSocket handling: Added
settledflag to properly handle timeout/open/error/close race conditions
Changes
- Faster retry loop: Reduced retry attempts from 30 to 5 since
maintainLoopretries every 3 seconds anyway - Allow own extension pages: Added
OUR_EXTENSION_IDSto allow attaching to our own extension pages while blocking other extensions
0.0.67
- Initial changelog