-
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 Brackets Live Development Issues with Chrome OSX #239
Comments
Comment by njx SO AWESOME. Thanks @fungl164! @redmunds, we should probably look around the various docs to find references to the "relaunch" dialog and remove them. The smoke tests are the main one that comes to mind, but there might be references in Getting Started, How to Use Brackets, etc. |
Comment by fungl164 @njx it feels good to give back to the community. Thank you guys putting out Brackets as well! re: "relaunch", you might also want to take a look at the _openInterstitialPage() sequence. In earlier trials I had a small patch which removed the need to reconnect the Inspector object using timeouts. For simplicity purposes, I took it out for this part, so it hasn't been tested well enough. |
Comment by njx Thanks. I wonder if we should mention in How to Use Brackets that we open a separate Chrome instance. Also, in the smoke tests, would it make sense to actually have the tester double-check that Chrome was opened in a separate profile? |
Issue by fungl164
Tuesday Nov 05, 2013 at 22:03 GMT
Originally opened as adobe#371
This provides better real-time detection/separation of Chrome debug sessions, as well as better connectivity + window/tab management from within Brackets.
fungl164 included the following code: https://github.com/adobe/brackets-shell/pull/371/commits
The text was updated successfully, but these errors were encountered: