docs(cli): clarify how to attach to an existing Chrome instance#1929
Closed
MukundaKatta wants to merge 3 commits intoChromeDevTools:mainfrom
Closed
docs(cli): clarify how to attach to an existing Chrome instance#1929MukundaKatta wants to merge 3 commits intoChromeDevTools:mainfrom
MukundaKatta wants to merge 3 commits intoChromeDevTools:mainfrom
Conversation
Contributor
Author
|
Withdrawing — low-value drive-by docs change. Apologies for the noise. |
This file contains hidden or 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
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.
Summary
chrome-devtools startdoes not accept--autoConnect--browserUrlwhen they want to attach to an already running Chrome instanceWhy
The CLI docs already describe supported daemon startup arguments, but it is easy to assume that
--autoConnectis available here as well. Calling out the intended--browserUrlworkflow makes the attachment path clearer for CLI users.