System shortcuts prevent usage of developer tools shortcuts
Reported by
davidbia...@gmail.com,
May 22 2017
|
||||
Issue description
Chrome Version : 58.0.3029.110
OS Version: OS X 10.12.5
URLs (if applicable) : n/a
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: n/a
Firefox 4.x: n/a
IE 7/8/9: n/a
What steps will reproduce the problem?
1. Open a page (that contains javascript sources)
2. Open the developer tools
3. Open a javascript file
4. Place a breakpoint
5. When at that breakpoint
6. Select something you want to 'evaluate in console' (or 'add to watch')
7. Try to use the shortcut CTRL-SHIFT-E (CTRL-SHIFT-A)
8. The shortcuts are not working
What is the expected result?
The shortcuts have the same result as the menu items in the right-click-menu
What happens instead of that?
Nothing
Please provide any additional information below. Attach a screenshot if
possible.
I am pretty sure by now that CTRL-SHIFT-E and CTRL-SHIFT-A are system wide shortcuts (on macOSX) to 'select from cursor to beginning of line' and 'select from cursor to end of line'.
I think that in the past the shortcuts were CMD-SHIFT-E and CMD-SHIFT-A (those are doing nothing, at least on my system)
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
,
May 24 2017
@hdodda I created a small screencast to demonstrate the issue better (Sorry for the unclear explanation the first time around): The breakpoint is not needed for example. 1. Open developer tools and open a .js file 2. Select code you want to investigate and use shortcut ctrl+shift+E/ctrl+shift+A 3. Observe that text get selected, but the functionality is not executed In the screencast you can first see what should happen when you press ctrl+shift+E and then what actually happens. Repeating this for ctrl+shift+A. The screenshot shows that the shortcuts are shown on the shortcuts panel.
,
May 24 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 24 2017
(Mac triage) Confirmed this. Dev tools, can you triage?
,
Jun 3 2017
,
Sep 22 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/crosutils/+/a5ed1df5341d9648ce9307364af5754c11db95e8 commit a5ed1df5341d9648ce9307364af5754c11db95e8 Author: Prathmesh Prabhu <pprabhu@chromium.org> Date: Fri Sep 22 09:02:00 2017 cros_vm_start: Accept extra arguments for qemu on commandline. We now accept extra arguments to cros_start_vm that are forwarded to the qemu invocation. This allows more complex virtual device setup to be done outside of the core vm starting script. A follow up CL will remove the moblab specific features from cros_vm_lib. Those features are moving to the 'cros moblabvm' command instead. BUG=chromium:725260 TEST=bin/cros_start_vm --image_file /some/image -- \ -net nic,macaddr=6c:3b:e5:16:c0:60 -net tap,ifname=tap001 Change-Id: I521a1701120b8bd24e68043885446e0f636436eb Reviewed-on: https://chromium-review.googlesource.com/648506 Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/a5ed1df5341d9648ce9307364af5754c11db95e8/lib/cros_vm_lib.sh [modify] https://crrev.com/a5ed1df5341d9648ce9307364af5754c11db95e8/bin/cros_start_vm |
||||
►
Sign in to add a comment |
||||
Comment 1 by hdodda@chromium.org
, May 23 2017Labels: Needs-Feedback
2.3 MB
2.3 MB View Download