Bugzilla

Making a better case here:

- For all other browser shortcuts, if the website does not intercept them, the browser handles them. Example would be Slack catching `Cmd-K`, preventing me from using the shortcut for awesomebar's tab switching. DevTools is a top-level browser feature and should adopt this paradigm.
- Low risk: Given the bubbling and cancelling of keyboard event, this would not break content but just catch more DevTools shortcuts that would be ignored when fired in content.
- Focus state is not something that is always clearly visible in the UI, so having devtools behave line a website, where users have to double-check that the content has focus is not an easy visual check but often requires a just-to-be-sure click in the UI.
- Some shortcuts in DevTools, like `Cmd-Shift-C` are handled globally and some not – and the UI does not show them any different.

Making a better case here:

- For all other browser shortcuts, if the website does not intercept them, the browser handles them. Example would be Slack catching `Cmd-K`, preventing me from using the shortcut for awesomebar's tab switching. DevTools is a top-level browser feature and should adopt this paradigm. The event bubbling order would be `content > devtools > browser`
- Low risk: Given the bubbling and cancelling of keyboard event, this would not break content but just catch more DevTools shortcuts that would be ignored when fired in content.
  - Commonly used shortcuts like `Delete`, `ESC` need some special considerations and testing and might only when with devtools focused
- Focus state is not something that is always clearly visible in the UI, so having devtools behave line a website, where users have to double-check that the content has focus is not an easy visual check but often requires a just-to-be-sure click in the UI.
- Some shortcuts in DevTools, like `Cmd-Shift-C` are handled globally and some not – and the UI does not show them any different.