Regression: Arrow key navigation doesn't work on chrome://downloads page.
Reported by
adha...@etouch.net,
Dec 8 2016
|
||||
Issue descriptionChrome Version: 56.0.2924.21 (Official Build)4d0fd85f092f947ef72046f62e953ecf44d5e64a-refs/branch-heads/2924@{#401} 32/64-bit. OS: Mac (10.10.5)(10.11.5), Windows (7,8,8.1,10), Linux(14.04 LTS) URL: http://www.thinkbroadband.com/download.html What steps will reproduce the problem? 1. Launch chrome, go to above URL and download 3-4 small files. 2. Navigate to chrome://downloads page and keep focus on first URL using 'Tab' key. 3. Now, press down arrow key from keyboard and observe the focus. Nothing happens on pressing down arrow key from keyboard. Focus should move to next URL on pressing down arrow key from keyboard. This is a regression issue, broken in M-50 series, below is manual regression range. Good build: 50.0.2657.0 Bad build: 50.0.2658.0 Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/8ef9022a0d352066587791b3e225ca264c688ade..2798da0054168aacd32e6c51c5a87befe415b1eb?pretty=fuller&n=100 Suspecting: r376895 Kindly review the attached screen-cast for reference.
,
Dec 15 2016
,
Dec 19 2016
adharap@, Could you please respond as per comment #1
,
Dec 19 2016
With response to comment #1: Retested the above issue on latest Canary chrome version 7.0.2956.0 (Official Build). It's still reproducible. i.e. after keeping the focus on first URL using 'Tab' key, focus is not moving to the next URL on pressing down arrow key from keyboard. Attaching screen-cast for the same.
,
Jan 2 2017
Still able to reproduce the issue on win10 chrome canary version 57.0.2969.0 dbeam, Could you please take a look
,
Jan 9 2017
Still able to reproduce the issue on win7 using chrome canary version 57.0.2976.0 dbeam, Could you please look into this issue.
,
Jan 17 2017
Just to update, still able to reproduce the issue on mac 10.12.2 using latest canary # 57.0.2983.0. dbeam@ - Could you please have a look into this issue. Thanks...!!
,
Jan 20 2017
dbeam@, Any update on this please
,
Feb 6 2017
,
Jul 6 2017
I'm no longer working on Chrome, and unlikely to fix any bug I'm currently assigned. So this bug doesn't languish, I'm unassigning myself. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kavvaru@chromium.org
, Dec 15 2016