Skip to content

docs: clarify offline emulation limits for WebSockets - #44058

Merged
Yury Semikhatsky (yury-s) merged 1 commit into
mainfrom
fix-44056-43057038208-1
Nov 12, 2026
Merged

Yury Semikhatsky (yury-s) merged 1 commit into
mainfrom
fix-44056-43057038208-1

Conversation

@microsoft-playwright-automation

Copy link
Copy Markdown
Contributor

The offline-emulation note groups WebSockets with HTTP requests, but its effect depends on the browser and whether a socket is already open.

Clarify that new connections fail in Chromium and Firefox, while established connections are not closed: Chromium can defer incoming messages until online, and Firefox can continue delivering them. Include WebKit's limits and warn against relying on offline emulation for message loss or connection closure. Browser behavior and the WebRTC guidance are unchanged.

Verified with fixture-based WebSocket probes in all three browsers, headed and headless, on macOS. npm run build and npm run flint passed.

Fixes #44056

Triaged on macOS by the Playwright bot - agent run

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "tests 1"

9496 passed, 262 skipped


Merge workflow run.

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "MCP"

2345 passed, 169 skipped


Merge workflow run.

@yury-s
Yury Semikhatsky (yury-s) marked this pull request as ready for review November 12, 2026 00:52
@yury-s
Yury Semikhatsky (yury-s) merged commit ed835d7 into main Nov 12, 2026
21 of 33 checks passed
@yury-s
Yury Semikhatsky (yury-s) deleted the fix-44056-43057038208-1 branch November 12, 2026 18:21
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.

[Bug]: browserContext.setOffline(true) does not affect established WebSockets in Firefox, and defers rather than fails them in Chromium

2 participants