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

Issue 657321 link

Starred by 5 users
Status: WontFix
Owner:
pfeldman@chromium.org
Closed: Nov 2016
Cc:
█ hdodda@chromium.org
nyerramilli@chromium.org
█ tkonch...@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: Keyboard shortcut (Ctrl+]) for navigating to next section is not working in devtools.

Reported by jshan...@etouch.net, Oct 19 2016 
Chrome Version: 56.0.2894.0 (Official Build) 9e01f1257eb75274157fe7d246869b32d24b155b-refs/heads/master@{#425838}-32/64 bit
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.10.5, 10.11.4)

Steps:
1. Launch Chrome and open devtools (F12) on NTP.
2. Press Ctrl+']' or '[' keys and observe.

Actual: No action is seen after pressing 'Ctrl+]' keys.

Expected: On pressing 'Ctrl+]' keys, next section of devtool i.e Console should be open.

This is a regression issue broken in M-56, will soon update bisect info.

Good Build: 55.0.2888.0 
Bad Build: 55.0.2889.0
Actual_video.mp4
443 KB View Download
Expected_video.mp4
450 KB View Download

Comment 1 by jshan...@etouch.net, Oct 19 2016 

Correction:
Good Build: 56.0.2888.0 
Bad Build: 56.0.2889.0

Comment 2 by tkonch...@chromium.org, Oct 19 2016

Labels: Needs-Bisect
Status: Untriaged (was: Unconfirmed)
Working on bisect. will provide the info soon.

Comment 3 by hdodda@chromium.org, Oct 19 2016

Cc: hdodda@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision
Owner: pfeldman@chromium.org
Status: Assigned (was: Untriaged)
Using the per-revision bisect providing the bisect results,
Good Build: 56.0.2888.0 (Revision : 424625)
Bad Build: 56.0.2889.0 (Revision : 424926)

You are probably looking for a change made after 424894 (known good), but no later than 424895 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/9d82356b6496bb090bd743be75774a9c4b9918e3..2cbfc042012e00bc5863caa8c55de9d25f71d5e3

From the CL above, assigning the issue to the concern owner 

@pfeldman - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Review URL :https://codereview.chromium.org/2412023002

Thanks !

Comment 4 by ranjitkan@chromium.org, Oct 19 2016

Labels: ReleaseBlock-Beta
Adding release block label, pleas undo if not the case.

Comment 5 by ajha@chromium.org, Oct 25 2016 

Friendly ping to get an update on this.

Comment 6 by kavvaru@chromium.org, Oct 28 2016 

Still able to reproduce the issue on windows 10 using chrome latest canary version 56.0.2902.0.

pfeldman@ Could you please look into this issue.

Comment 7 by pfeldman@chromium.org, Nov 2 2016

Labels: -Pri-1 -ReleaseBlock-Beta Pri-2

Comment 8 by tkonch...@chromium.org, Nov 17 2016 

Still able to reproduce the issue on windows 10 using chrome latest canary version 56.0.2922.0

pfeldman@, Could you please take a look

Comment 9 by pfeldman@chromium.org, Nov 21 2016

Status: WontFix (was: Assigned)
Handling of Ctrl+[ was removed deliberately on our way to generic accessibility / keyboard navigability.
►

Sign in to add a comment