New issue
Advanced search Search tips

Issue 681352 link

Starred by 2 users
Status: Duplicate
Merged: issue 644227
Owner: ----
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

WASD navigation of dev tools timeline doesn't work well for non-standard keyboard layouts

Reported by ben.low...@a8c.com, Jan 15 2017 
Chrome Version       : 55.0.2883.95 (64-bit)
URLs (if applicable) : 
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: NA
    Firefox: NA
         IE: NA

What steps will reproduce the problem?
(1) Open settings > keyboard prefs > input sources on a mac
(2) Add the Colemak layout. Make it active.
(3) Open a saved timeline in dev tools
(4) Try to use the WASD style keyboard navigation. Unfortunately, WASD in Colemak is WARS. 
(5) Cry a little.

What is the expected result?
I expected WARS to navigate like WASD does on a QWERTY layout

What happens instead?
WA are in the right places. SD are not.

Please provide any additional information below. Attach a screenshot if
possible.

Comment 1 by durga.behera@chromium.org, Jan 16 2017

Labels: -Type-Bug M-57 Type-Feature
Status: Untriaged (was: Unconfirmed)
Was able to reproduce the issue on Mac 10.12.2 using 55.0.2883.95,57.0.2982.0 and prior to M54 was bale to load the saved timeline file.

Requesting the Devtool folks to take a look into this if it can be supported.
Looks like a feature request.

Comment 2 by ben.low...@a8c.com, Jan 16 2017 

Yeah, sorry if this is under the wrong thing. I wasn't quite sure where to submit a feature request.

Comment 3 by ben.low...@a8c.com, Jan 16 2017 

Just a note, this is probably affecting Dvorak (and Workman / etc) folks too. Unsure if  / how it affects folks using far east layouts.

Comment 4 by caseq@chromium.org, Jan 17 2017

Mergedinto: 644227
Status: Duplicate (was: Untriaged)
This should hopefully be fixed along with  issue 644227 , please let us know if it still does not work.

Comment 5 by vandenbe...@gmail.com, Jan 17 2017 

Hi Ben. This should, like Caseq said, be fix with #644227.
You can test this in current Chrome Canary (57). Let me know if some keyboard layout doesn't work. The solution should be layout agnostic.
►

Sign in to add a comment