Chrome Version       : 50 - 53.0.2746.0 canary 
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1) Open Sources tab in DevTools and brows to any website that uses external JS/CSS files
(2) Open 2 CSS/JS files in Sources.
(3) Click on the second file you opened to focus the cursor within that Sources editor window
(4) Type CMD-w (Mac) or CTRL-w (Windows)

What is the expected result?

The second file editor you opened should close, leaving 1 editor window open

What happens instead?

The entire Chrome tab closes, and I lose my debugging workflow

Please provide any additional information below. Attach a screenshot if
possible.

@pbakaus We discussed this at I/O 2016 during the Chrome Office Hours and you recommended that I file this bug.  Given that the Sources editor tabs behave like our native code editors, we should expect it to behave similar to an editor.  I'm a fan of DevTools Workspaces and often save time by editing JS/CSS directly in Sources.  However, muscle memory habits like CMD-w click in when I have multiple Sources files open that I no longer need.  Then my entire DevTools workspace is closed accidentally, which takes numerous steps to recreate again.

If CMD-SHIFT-P mimics Sublime's Command Palette, it would be great if CMD-w mimics the "close active tab where the cursor is focused" behavior.
 

Deleted: cmd-w-closes-chrome.png 895 KB

	cmd-w-closes-chrome.png 895 KB View Download