Proposal: add documentation about what keywords to use for each key when customizing keybindings (eg: binding key shortcuts to "pageup" and "pagedown" fails.)

[Harmonia2Side]

Hello there;
I have been attepting to map the shortcuts to a combination with the "page up" and "page down" keys, but they do not appear to work. Aditionally, logseq reports the following error when restarting:

plugin.logseq-tabs/tabs-select-prev alt+pgup Keyboard shortcut conflicts with existing shortcut: plugin.logseq-tabs/tabs-select-next

which leads me to believe that I am using the wrong keywords for the keys.

What I have tried:

• I've tried the following combinations on the config file, all of which did not succeed:

"tabs:select-next": "alt+pgdn",
  "tabs:select-prev": "alt+pgup",

  "tabs:select-next": "alt+PageDown",
  "tabs:select-prev": "alt+PageUp",

  "tabs:select-next": "alt+pagedown",
  "tabs:select-prev": "alt+pageup",

  "tabs:select-next": "alt+pgdown",
  "tabs:select-prev": "alt+pgup",

• I have also tried taking a look at the code to identify what functions and libraries are being used to capture and process the keystrokes, and then search for some documentation on what keywords they expect for each keys. Unfortenatly, my javascript/typescript skills don't seem to be enough to figure this out by the code either.

Conclusion

This is not really a big problem. I've mapped the shortcut to other keys that have satisfactory workflow performance. However, it would be nice to have a mapping list of which keywords match with each keys, and add it to the documentation (perhaps in the README, or maybe a separate "keycode-mapping-sheet.txt" file for example).

If someone could show me how to figure out the keycodes by looking at the right places at the code, I could do such a documentation file and make a pull request to add it.