diff --git a/extension/CHANGELOG.md b/extension/CHANGELOG.md index 4c34ab9..e57d633 100644 --- a/extension/CHANGELOG.md +++ b/extension/CHANGELOG.md @@ -1,5 +1,11 @@ # Changelog +## 0.0.73 + +### Bug Fixes + +- **Service worker keepalive via chrome.alarms**: Added `chrome.alarms` keepalive to prevent Chrome MV3 from terminating the service worker when idle. Without this, the `maintainLoop` stops, the WebSocket closes, and the extension silently disconnects from the relay server — causing `session new` to fail with "Extension did not connect within timeout." + ## 0.0.72 ### Bug Fixes diff --git a/extension/manifest.json b/extension/manifest.json index da15201..a5a4d19 100644 --- a/extension/manifest.json +++ b/extension/manifest.json @@ -1,9 +1,10 @@ { "manifest_version": 3, "name": "Playwriter", - "version": "0.0.72", + "version": "0.0.73", "description": "Automate your Browser using Cursor, Claude, VS Code. More capable and context efficient than Playwright MCP.", "permissions": [ + "alarms", "debugger", "tabGroups", "contextMenus", diff --git a/extension/src/background.ts b/extension/src/background.ts index f8428ec..2924af4 100644 --- a/extension/src/background.ts +++ b/extension/src/background.ts @@ -1483,6 +1483,18 @@ async function onActionClicked(tab: chrome.tabs.Tab): Promise { resetDebugger() connectionManager.maintainLoop() +// MV3 service workers can be terminated by Chrome despite setInterval. +// chrome.alarms is the only reliable way to keep a service worker alive. +// Without this, the maintainLoop stops, the WebSocket closes, and the +// extension silently disconnects from the relay server. +chrome.alarms.create('keepalive', { periodInMinutes: 0.25 }) +chrome.alarms.onAlarm.addListener((alarm) => { + if (alarm.name === 'keepalive') { + // No-op — the alarm firing is enough to wake the service worker. + // The maintainLoop will handle reconnection if needed. + } +}) + chrome.contextMenus .remove('playwriter-pin-element') .catch(() => {}) diff --git a/playwriter/CHANGELOG.md b/playwriter/CHANGELOG.md index e0e8b5b..edf38a0 100644 --- a/playwriter/CHANGELOG.md +++ b/playwriter/CHANGELOG.md @@ -1,7 +1,37 @@ # Changelog +## 0.0.84 + +### Docs + +- **Remove click-timeout section from `skill.md` mistakes list**: Deleted the dedicated post-click timeout section per docs cleanup request and renumbered the following mistake item. + +## 0.0.83 + +### Docs + +- **Correct click-timeout guidance in `skill.md`**: Replaced the incorrect "SPA does not fire load" explanation with the actual behavior: click succeeds, then Playwright times out during post-click navigation waiting when action timeout budget is exceeded. + +## 0.0.82 + +### Improvements + +- **Increase default action timeout to 60s**: Raised `context.setDefaultTimeout` from `5000ms` to `60000ms` to avoid false click failures on slower real-world flows where the interaction succeeds but Playwright post-action navigation waiting exceeds short budgets. + +## 0.0.81 + +### Improvements + +- **Increase default action timeout to 5s**: Raised `context.setDefaultTimeout` from `2000ms` to `5000ms` to reduce false `locator.click()` timeouts on slower navigation flows (for example GitHub/Turbo links) where the click succeeds but post-click navigation settling exceeds 2 seconds. Default navigation timeout remains `10000ms`. + ## 0.0.80 +### Bug Fixes + +- **Relaxed relay server version check timeout**: Increased `getRelayServerVersion` timeout from 500ms to 2000ms to prevent false "server not running" detections that kill a healthy relay server and disconnect the extension. This was causing intermittent `session new` failures when the relay was briefly busy (e.g. processing recording chunks). + +## 0.0.80 (previous) + ### Improvements - **Descriptive click timeout errors**: When `locator.click()` times out due to actionability failures, the error now includes the reason (e.g. "Element is not visible", "Element is not stable", "