Updating readme and launch position

Author: CodeMooseUS

README.md

@@ -8,10 +8,10 @@ A VSCode extension to host the chrome devtools inside of a webview.
     </a>
 </p>
 
-## Attach to a running chrome instance:
+## Attaching to a running chrome instance:
 ![Demo1](demo.gif)
 
-## Launch a chrome debugger project and use screencasting:
+## Launching a 'debugger for chrome' project and using screencast:
 ![Demo2](demo2.gif)
 
 # Using the extension
@@ -32,7 +32,9 @@ A VSCode extension to host the chrome devtools inside of a webview.
 
 # Known Issues
 - Prototyping stage
-- Settings in the devtools are not persisted
+- Having the DevTools in a non-foreground tab can cause issues while debugging
+    - This is due to VS Code suspending script execution of non-foreground webviews
+    - The workaround is to put the DevTools in a split view tab so that they are always visible while open
 - Chrome browser extensions can sometimes cause the webview to terminate
 
 # Developing the extension itself

demo2.gif

@@ -173,12 +173,12 @@ class DevToolsPanel {
     private _disposables: vscode.Disposable[] = [];
 
     public static createOrShow(context: vscode.ExtensionContext, targetUrl: string) {
-        const column = vscode.window.activeTextEditor ? vscode.window.activeTextEditor.viewColumn : undefined;
+        const column = vscode.ViewColumn.Beside;
 
         if (DevToolsPanel.currentPanel) {
             DevToolsPanel.currentPanel._panel.reveal(column);
         } else {
-            const panel = vscode.window.createWebviewPanel('devtools-for-chrome', 'DevTools', column || vscode.ViewColumn.Two, {
+            const panel = vscode.window.createWebviewPanel('devtools-for-chrome', 'DevTools', column, {
                 enableScripts: true,
                 enableCommandUris: true,
                 retainContextWhenHidden: true