New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 815929 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Sep 13
Cc:
█ sindhu.chelamcherla@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug



Sign in to add a comment

Move Tab keys (Ctrl-PgUp/PgDn) stop working after reloading a crashed tab

Project Member Reported by thomasvs@google.com, Feb 24 2018 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36

Steps to reproduce the problem:
1. go to a crashed tab, or kill one
2. hit ctrl-r to reload
3. hit ctrl-pgup to move to the next tab

What is the expected behavior?
should move to the next tab

What went wrong?
ctrl-pg up and pg dn do not react/move tabs, until you do at least one mouse click in the browser window.

Did this work before? Yes a few versions ago

Chrome version: 64.0.3282.167  Channel: stable
OS Version: trusty
Flash Version: Shockwave Flash 28.0 r0

makes it a lot more tiresome to recover a bunch of oom-killed tabs.

Comment 1 by woxxom@gmail.com, Feb 24 2018 

FWIW Chrome in Windows never allowed keyboard input immediately after reloading a crashed tab.
There's a workaround though: press Alt key twice.

Comment 2 by thomasvs@google.com, Feb 24 2018 

I'll try the workaround.  But that's going to be hard to remember.

Are you saying it's a deliberate feature to not allow keyboard input after reloading a crashed tab?

Comment 3 by thomasvs@google.com, Feb 24 2018 

tried hitting alt twice, didn't work - still can't ctrl-pgup/pgdn

Comment 4 by susan.boorgula@chromium.org, Feb 25 2018

Labels: Needs-Triage-M64 Needs-Bisect

Comment 5 by sindhu.chelamcherla@chromium.org, Feb 26 2018

Cc: sindhu.chelamcherla@chromium.org
Components: -UI UI>Input>KeyboardShortcuts
Labels: -Needs-Bisect -Type-Bug-Regression Triaged-ET M-66 FoundIn-66 Target-66 OS-Windows Type-Bug
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version 64.0.3282.167 using Windows 10, Ubuntu 14.04. This issue is seen from M-60. Hence considering this issue as Non-Regression and marking as Untriaged.

Comment 6 by robliao@chromium.org, Sep 13

Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
►

Sign in to add a comment