Starting a "Chrome Debug" session does not work when chrome is already open #1327
Comments
Si-So
added a commit
to Si-So/wildwebdeveloper
that referenced
this issue
Sep 8, 2023
…rted even when a chrome window is already open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Exact same steps as described in #1294 except before starting the "Chrome Debug" session open a chrome window.
Instead of opening a new chrome instance, a new empty tab is opened in the running chrome window. wwd is not apple to connect to this chrome instance.
Environment
Eclipse 2023-06
wwd 1.3.0
I tested this both on Windows 11 and Ubuntu 20
Analysis
Since the chrome instance was not started with remote debugging enabled, wwd is not able to connect.
Workaround
As already mentioned in #1294: Close all chrome windows before starting a "Chrom Debug" session.
This workaround is problematic, because it might interrupt a developer's normal workflow.
Related issues
#927 is probably related. The difference in #927 is that the error occurs when starting a "Running Chrome Debug Instance" debug session and not a "Chrome Debug" session.
The text was updated successfully, but these errors were encountered: