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 bug that debugger sometimes doesn't open Chrome automatically #445

Merged
merged 1 commit into from
Dec 17, 2021

Conversation

ono-max
Copy link
Collaborator

@ono-max ono-max commented Dec 17, 2021

Debugger sometimes doesn't open Chrome automatically because the debugger doesn't wait for the response of 'Page.navigate' method. This PR fixes it.

The reason is that the debugger doesn't wait for the response of 'Page.navigate' method
@ko1 ko1 merged commit 226fa43 into ruby:master Dec 17, 2021
ono-max referenced this pull request in ono-max/debug Dec 18, 2021
#445 was an ad hoc solution and this commit fixes it correctly

The reason of the bug is that the debugger doesn't call 'Page.enable'
@ono-max ono-max mentioned this pull request Dec 18, 2021
ko1 pushed a commit that referenced this pull request Dec 18, 2021
#445 was an ad hoc solution and this commit fixes it correctly

The reason of the bug is that the debugger doesn't call 'Page.enable'
@ono-max ono-max deleted the patch-7 branch December 22, 2021 03:16
ono-max referenced this pull request in ono-max/debug Dec 23, 2021
Chrome sometimes fails to get the frame id when it navigates current page to the given URL

This is related to #445
ono-max referenced this pull request in ono-max/debug Dec 23, 2021
Chrome sometimes fails to get the frame id when it navigates current page to the given URL

This is related to #445
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants