A UX feature request. Not sure what would be the best way to expose such functionality though.

In devtools settings under Sources there are already about 13 different settings, 8 checkboxes and two dropdowns. I would suggest adding another option "Enable source editing"

Though I guess I can do this myself, I think I saw somewhere that somebody had written an extension to inject code into the devtools.

While I can relate to this issue, adding another setting to already large and intractable list of settings doesn't seem like it'll solve the issue for most people.

This seems more like an issue of focus management. Is there any particular reason the source window is gaining focus when the debugger pauses? Are there debugging keyboard shortcuts that are only valid if the editor has focus?

If not, I think a better solution would be to not switch focus when the debugger pauses. In this case, if focus was in the console before the exception was raised, it will remain so after. If the Sources panel wasn't active, it could be brought to the foreground and a more benign element (e.g the debugger toolbar) could be given focus.

Andrey, what do you think about this?

Issue 883644 has been merged into this issue.

Note that 883644 is not about hitting a break point but about simply changing a file externally, in my case with vim... Chrome rudely grabs focus resulting subsequent keystrokes changing the file in Chrome.

I think it is a mistake to merge 883644 into this issue - they really aren't the same thing, imo. Please consider 'unmerging' them.