-
Notifications
You must be signed in to change notification settings - Fork 127
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
Open Chrome automatically #334
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ono-max
force-pushed
the
open-chrome-automatically
branch
5 times, most recently
from
October 19, 2021 08:12
7178fcf
to
a9960cb
Compare
ko1
reviewed
Oct 19, 2021
ono-max
force-pushed
the
open-chrome-automatically
branch
8 times, most recently
from
October 24, 2021 09:22
c5f5322
to
7bf2944
Compare
ono-max
force-pushed
the
open-chrome-automatically
branch
2 times, most recently
from
October 24, 2021 10:26
cb6f524
to
98c6d6b
Compare
ko1
reviewed
Oct 24, 2021
ono-max
force-pushed
the
open-chrome-automatically
branch
from
October 24, 2021 23:54
98c6d6b
to
be28829
Compare
ono-max
force-pushed
the
open-chrome-automatically
branch
from
October 25, 2021 00:27
be28829
to
8dad621
Compare
ko1
reviewed
Oct 25, 2021
ko1
reviewed
Oct 25, 2021
ko1
reviewed
Oct 25, 2021
ono-max
force-pushed
the
open-chrome-automatically
branch
3 times, most recently
from
October 26, 2021 12:28
9bfc28f
to
1390694
Compare
ono-max
force-pushed
the
open-chrome-automatically
branch
2 times, most recently
from
October 27, 2021 10:48
afde07d
to
2360481
Compare
ko1
reviewed
Oct 28, 2021
ono-max
force-pushed
the
open-chrome-automatically
branch
from
October 28, 2021 23:08
2360481
to
f04a4a4
Compare
ono-max
force-pushed
the
open-chrome-automatically
branch
2 times, most recently
from
December 7, 2021 00:46
5557fdc
to
e87b5b7
Compare
ono-max
force-pushed
the
open-chrome-automatically
branch
2 times, most recently
from
December 8, 2021 08:36
237e9a3
to
a1d916c
Compare
ono-max
force-pushed
the
open-chrome-automatically
branch
from
December 8, 2021 08:43
a1d916c
to
5d2ab5e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To use Chrome debugging, we need the following steps.
rdbg --open=chrome target.rb
Source
pane.The steps are long, so I implemented the setup method for Chrome to open the Chrome browser automatically. We can use Chrome debugging as follows:
Source
pane.The following video shows an example of this PR.
Screen.Recording.2021-10-23.at.20.26.24.mov
Note that I'll refactor the process for WebSocket.