Bind to physical keys or bind per layout for multi-layout users

[eugenesvk]

Is it possible to bind to physical, layout independent keys?

Or as a workaround: per-layout keys (so a set of keybindings that would only work in a single layout)?

Currently, if you're using two latin layouts, you'll have a muscle memory conflict, which at least you could resolve if you could define keys tied to a layout.

If you're using non-Latin layout, then the Latin definitions don't work with tbkeys, even though the underlying library works on this page https://craig.is/killing/mice for key X at least, which doesn't work with tbkeys in a non-latin layout

Then for some common keys you have the same issue as with two latin layouts - you can't fix a keybind to be consistent for your muscle memory

[morat523035]

I guess you would need to hack the addon to support layout independent keys.

More info on Mousetrap hack
http://www.perplexity.ai/search/can-the-mousetrap-standalone-l-4.h3eMz6SWWOjZupi9Qn4g

// run code in Thunderbird Error Console, then press q in main window to test
document.addEventListener('keydown', function (event) {
  console.log(event.code); // "KeyQ"
  console.log(event.key); // "a" for AZERTY, "q" for QWERTY
}, {once: true});

Regarding per-layout keys. Does the language change when you change the layout?

// run code in Thunderbird Error Console to test
console.log(navigator.language); // "fr-FR" for AZERTY, "en-US" for QWERTY

// Thunderbird does not support navigator.keyboard property
// run code in Google Chrome DevTools Console tab to test
navigator.keyboard.getLayoutMap().then(function (keyboardLayoutMap) {
  var upKey = keyboardLayoutMap.get("KeyQ");
  console.log(upKey); // "a" for AZERTY, "q" for QWERTY
});

Similar issue
http://github.com/wshanks/tbkeys/issues/182

Just to clarify, I'm not the developer of this addon, just another user sharing my perspective.