New issue
Advanced search Search tips

Issue 862766 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Task Manager keyboard shortcut not working

Reported by alexande...@gmail.com, Jul 11

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. Press Shift+Esc to bring up Task Manager
2. Nothing happens

What is the expected behavior?
Shift+Esc should open Task Manager

What went wrong?
This keyboard shortcut (Shift+Esc) just doesn't seem to work anymore.  The Task Manager still works fine when opened from the menu (More tools > Task Manager).  All other keyboard shortcuts also work fine (e.g. Ctrl+Tab, Ctrl+Shift+N, etc). The Esc key works fine by itself (removes focus from a focused element).  The Shift key also works fine (obviously, since I'm able to type capital letters :))

Did this work before? Yes Can't remember exactly, but this stopped working at least half a year ago, perhaps longer

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 8.1
Flash Version:
 
Labels: Needs-Bisect Needs-Triage-M67
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on reported chrome version 67.0.3396.99 using Windows 10 & 7 as of now we don't have Windows 8.1. Attaching screen-cast for reference.
Steps: 
---------
1. Launched reported chrome 
2. Launched Task Manager by hitting >> Shift+Esc  
As we are able to Task Manager.

@Reporter: Request you to retry this issue with fresh profile without any extensions/apps or reset all the flags and let us know if issue still persists.

Thanks.!
862766.mp4
891 KB View Download
I can reproduce this on my Mac.
Cc: vamshi.kommuri@chromium.org
Labels: Hotlist-DesktopUIChecked
Status: WontFix (was: Unconfirmed)
**UI mass Triage**

We were unable to reproduce this bug. If this bug still reproduces for you, please reopen or file a new issue.

Thanks!

Sign in to add a comment