You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To run E2E test cases follow instructions on README.md
1 of 4 test cases will fail and shows the defect (missing Accept-Language header while switch from HTTP to websocket connection between client and server)
Expected behavior
Chromium and Firefox are respecting the localized context during whole test run
on first load of website via HTTP request
on later performed switch from HTTP to websocket (GET request with Upgrade: websocket header)
Website is loaded with correct language via HTTP and websocket
All 4 E2E test cases passes
Actual behavior
Firefox:
The two test cases with Firefox passes as expected (Accept-Language header is respected all the time)
Chromium:
Chromium respects the localized context as the Accept-Language header is sent while website is loaded via HTTP
Chromium DOES NOT respect the localized context as the Accept-Language header is missing when Blazor application requests the switch to websocket (GET request with Upgrade: websocket header)
One test case with Chromium still passes (as English is requested and English is default language > so missing Accept-Language header doesn't influence the test result)
Second test case with Chromium fails where German is requested via Accept-Language header:
Website is first loaded in German via HTTP
After a short time website switches to websocket and is loaded again with English as default language
Additional context
Using web-application with a real Chrome browser doesn't show this behavior. Here is the Accept-Language header also in place during the switch from HTTP to websocket. So seems to be specific to Chromium in Playwright.
Behavior could be reproduced with Windows 11 and with Ubuntu 22.04 (WSL)
Network details (HTTP header details) is given on README.md
@mxschmitt: Is the implementation of the browser (Chromium, Firefox etc.) the same for Playwright Node.js and .NET?
As #13919 is open for 2 years now - do you see any chance that this will be fixed?
Version
1.43.0
Steps to reproduce
Expected behavior
Actual behavior
Additional context
Environment
The text was updated successfully, but these errors were encountered: