Interesting. We could do this assuming it's really straightforward.

Have you a recommendation on how to handle this? The keyboard bindings are all in javascript, so assuming you've done this in your work, we can adapt the same approach.

I would suggest editing the FlameChart._handleZoomPanKeys function (
https://cs.chromium.org/chromium/src/third_party/WebKit/Source/devtools/front_end/ui_lazy/FlameChart.js?l=1002) from using KeyboardEvent.keyCode to KeyboardEvent.code.

According to the documentation on MDN, Keyboard.code should be the appropriate way to program game controles because it represent the physical location of the key opposed to the character generated by the pressed key: https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code

The code change would look something like this:

     var zoomMultiplier = e.shiftKey ? 0.8 : 0.3;
     var panMultiplier = e.shiftKey ? 320 : 80;
-    if (e.keyCode === "A".charCodeAt(0)) {
+    if (e.code === "KeyA") {
         this._handlePanGesture(-panMultiplier * this._pixelToTime);
         e.consume(true);
-    } else if (e.keyCode === "D".charCodeAt(0)) {
+    } else if (e.code === "KeyD") {
         this._handlePanGesture(panMultiplier * this._pixelToTime);
         e.consume(true);
-    } else if (e.keyCode === "W".charCodeAt(0)) {
+    } else if (e.code === "KeyW") {
         this._handleZoomGesture(-zoomMultiplier);
         e.consume(true);
-    } else if (e.keyCode === "S".charCodeAt(0)) {
+    } else if (e.code === "KeyS") {
         this._handleZoomGesture(zoomMultiplier);
         e.consume(true);
     }

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/52b4d80a29a24607e74ed1a9f3466208f98ebf62

commit 52b4d80a29a24607e74ed1a9f3466208f98ebf62
Author: vandenberghe.jeroen <vandenberghe.jeroen@gmail.com>
Date: Thu Oct 20 00:19:48 2016

DevTools: Make Timeline navigation keyboard layout agnostic (WASD/ZQSD)

On QWERTY keyboards you can use the WASD keys to pan and zoom
the timeline flamechart.
On other keyboard layouts those keys aren't placed very intuitive.

Keyboard.code should be the appropriate way to program game-alike
controles because it represent the physical location of the key opposed
to the character generated by the pressed key: https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code

BUG= 644227 

Review-Url: https://chromiumcodereview.appspot.com/2431773002
Cr-Commit-Position: refs/heads/master@{#426349}

[modify] https://crrev.com/52b4d80a29a24607e74ed1a9f3466208f98ebf62/AUTHORS
[modify] https://crrev.com/52b4d80a29a24607e74ed1a9f3466208f98ebf62/third_party/WebKit/Source/devtools/front_end/timeline/TimelinePanel.js
[modify] https://crrev.com/52b4d80a29a24607e74ed1a9f3466208f98ebf62/third_party/WebKit/Source/devtools/front_end/ui_lazy/ChartViewport.js

 Issue 681352  has been merged into this issue.