New issue
Advanced search Search tips

Issue 793724 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 19
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Keyboard shortcut to inspect element in developer console is confusing on Linux

Reported by l...@paytouch.io, Dec 11 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Select some text
2. Try to copy, accidentally pressing Ctrl + Shift + C
3. Disable 'Inspect Element' mode
4. Go to step 1, and try not mashing the keyboard this time

What is the expected behavior?

What went wrong?
On Linux both Ctrl + C and Ctrl + Shift + C are commonly used as shortcuts for copying the selected item to the system clipboard. I understand there are other shortcuts to copy text, but if a user has recently switched to Linux, these will probably be ingrained in their muscle memory.

If you select text in Chromium and try to copy, accidentally pressing Ctrl + Shift + C,  it will open the developer console and trigger 'Inspect Element' mode. To cancel this you can either press the keyboard shortcut again, or click the button in the developer console, but either of these will cause the focus to be lost, which means you have to select the text again. This behaviour is confusing and breaks your flow.

I'd suggest changing the shortcut for this mode, so accidentally pressing Ctrl + Shift + C doesn't trigger unexpected behaviour (having it do nothing is probably good enough). However given 'Inspect Element' mode is predominately mouse-orientated, I'm not sure if it really makes sense to have a keyboard shortcut for this, so maybe it can be removed.

Did this work before? No 

Chrome version: 62.0.3202.94  Channel: n/a
OS Version: Arch
Flash Version:
 
Labels: Needs-Triage-M62
Components: Platform>DevTools>UX
Status: Untriaged (was: Unconfirmed)
Owner: pfeldman@chromium.org
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
That's so for historical reasons.

Sign in to add a comment