Skip to content
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

fix: The 'WebSocket connection closed' error on Chrome 130 #8297

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

PavelMor25
Copy link
Collaborator

@PavelMor25 PavelMor25 commented Oct 14, 2024

Purpose

When requesting active tabs in Chrome 130.0.6723.6, a chrome-extension tab is included in the list. A CDP client is created based on this tab, but the tab gets closed, which results in the error.

Approach

Excluded tabs with ^chrome-extension URLs from the list of tabs.

References

closes #8286

Pre-Merge TODO

  • Write tests for your proposed changes
  • Make sure that existing tests do not fail

@testcafe-need-response-bot testcafe-need-response-bot bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 14, 2024
@PavelMor25 PavelMor25 removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 14, 2024
@PavelMor25 PavelMor25 marked this pull request as ready for review October 14, 2024 12:16
@PavelMor25 PavelMor25 merged commit 82a57ef into DevExpress:master Oct 16, 2024
21 checks passed
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.

Tests fail with "Error: WebSocket connection closed" for Chrome 130.0.6723.6 (2024-09-18)
3 participants