-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Fix chrome launching problems #2916
Comments
Comment by gruehle
|
Comment by redmunds
You need to use randy/starting-live-dev branches on both brackets and brackets-shell. Then try starting Live Dev in these cases:
Also test updating CSS and HTML in Brackets. |
Comment by redmunds
|
Comment by DennisKehrig All Chromes closed: works. Crashed on exit once, but that seems to be the older, hard to reproduce bug. |
Comment by DennisKehrig Changed appshell_extensions_win.cpp to use "--user-data-dir=brackets-profile2" - same thing as I said in my email: Chrome tries to import stuff from Firefox (and fails, presenting an error dialog that delays the process and causes Brackets to timeout if not dismissed soon enough), afterwards .html files open with Chrome if double-clicked. Same thing with "--no-default-browser-check", sadly. |
Comment by redmunds
|
Comment by gruehle Glad you got the first launch problem solved! Merging. |
Issue by redmunds
Monday Mar 11, 2013 at 20:23 GMT
Originally opened as adobe/brackets#3098
This is for adobe/brackets#2370
This changes Brackets to always set enableRemoteDebugging to true. This only seems to effect Windows, but it's changed for both Mac and Windows, so both should be tested.
There is an associated randy/starting-live-dev branch on brackets-shell.
@
gruehle - there is a remaining issue that@
DennisKehrig had on WinXP where he reported that his default browser was forced to be Chrome. I was prompted to change default browser on Win7, so I asked him to double-check that this is a real issue.redmunds included the following code: https://github.com/adobe/brackets/pull/3098/commits
The text was updated successfully, but these errors were encountered: