precondition

I think I understand it better now. Now, it only happens sporadically; there is a timing problem. My keyboard firmware sends macros involving modifier+key at superhuman speeds and AutoKey seemingly...

`xev` output of macro key ``` KeyPress event, serial 37, synthetic NO, window 0x5000001, root 0x55b, subw 0x0, time 5516034, (98,93), root:(809,466), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen...

This might interest you: https://github.com/hajimen/kle_scraper

You can checkout my PR for right hand modifier support in LM: https://github.com/qmk/qmk_firmware/pull/13085

I'd add an explanation of what the numbers after [TRACE] mean in the docs page on unit tests. It's not obvious that it is a timestamp.

That's a long title.

Hm, interestingly, the tester page doesn't apply the OS keyboard layout on page load so it falls back to `store/modules/keycodes/ansi.js` and `store/modules/keycodes/iso.js` which contain lowercase `name` fields like `{ name:...

Despite the multi-layout awareness, “Handle typing” and “Detects chatter” still require https://github.com/qmk/qmk_configurator/pull/1186 to pass.

Yes, the capital P can now be found.

Bump