-
Notifications
You must be signed in to change notification settings - Fork 22
largeMessage test fails on chrome #105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It seems that chrome does not handle messages containing |
Seems it simply drops these characters. Minimum reproducible example: https://github.com/gzm0/chrome-webdriver-js-string |
Wow, nice investigation! |
Interesting. Perhaps some INT8/UINT8 issues then. |
So just FTR: My preference would be to have this issue solved on the chromedriver end. If necessary, we can work around it by encoding things differently when passing them back from the browser (this workaround would affect all browser types though). There is currently no workaround that can be applied by users only. |
I've switched the tests causing #119 to Firefox which is working fine. So I guess we can wait until this is fixed in chromedriver. |
The upstream issue [1] has been fixed in Chrome 89, which has just hit the GitHub Actions virtual environment [2]. [1]: https://bugs.chromium.org/p/chromedriver/issues/detail?id=3672 [2]: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F20210309.1
No description provided.
The text was updated successfully, but these errors were encountered: