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

Fix chrome launching problems #3098

Merged
merged 3 commits into from
Mar 14, 2013
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions src/LiveDevelopment/LiveDevelopment.js
Original file line number Diff line number Diff line change
Expand Up @@ -557,15 +557,9 @@ define(function LiveDevelopment(require, exports, module) {
if (!browserStarted && exports.status !== STATUS_ERROR) {
url = launcherUrl + "?" + encodeURIComponent(url);

// If err === FileError.ERR_NOT_FOUND, it means a remote debugger connection
// is available, but the requested URL is not loaded in the browser. In that
// case we want to launch the live browser (to open the url in a new tab)
// without using the --remote-debugging-port flag. This works around issues
// on Windows where Chrome can't be opened more than once with the
// --remote-debugging-port flag set.
NativeApp.openLiveBrowser(
url,
err !== NativeFileError.ERR_NOT_FOUND
true // enable remote debugging
)
.done(function () {
browserStarted = true;
Expand Down