Skip to content
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.

Fix chrome launching problems #215

Merged
merged 7 commits into from
Mar 14, 2013
Merged

Fix chrome launching problems #215

merged 7 commits into from
Mar 14, 2013

Conversation

redmunds
Copy link
Contributor

This is for adobe/brackets#2370

This adds a new launch flag so chrome uses a different profile on Window. This causes Chrome to open a separate window for brackets Live Preview connections which avoids debugging flag conflicts.

This didn't seem to have any effect on Mac, so it wasn't added.

There is an associated randy/starting-live-dev branch on brackets.

@gruehle
Copy link
Member

gruehle commented Mar 12, 2013

I'm seeing a bug with this change:

  1. Have Chrome open with tabs loaded
  2. Start a Live Preview session (opens a new window as expected)
  3. Open a new tab in the newly opened window
  4. Stop the Live Preview session
  5. Start Live Preview session again

At step 4, the file is opened in the original Chrome window from Step 0, and not the Chrome window from step 1. Brackets shows the "Connecting to Browser" error dialog. Clicking "Relaunch Chrome" closes both windows.

@gruehle
Copy link
Member

gruehle commented Mar 12, 2013

Ignore the previous comment -- I didn't have the randy/starting-live-development branch checked out in the brackets repo. Everything is working fine on Windows.

@ghost ghost assigned gruehle Mar 12, 2013
@gruehle
Copy link
Member

gruehle commented Mar 14, 2013

Glad you got the first launch problem solved! Merging.

gruehle added a commit that referenced this pull request Mar 14, 2013
@gruehle gruehle merged commit 37a5158 into master Mar 14, 2013
@gruehle gruehle deleted the randy/starting-live-dev branch March 14, 2013 14:29
gruehle added a commit that referenced this pull request Dec 8, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants