💻 Support for MacOS option key

[bradystroud]

Hi,

• [x] Add support for the MacOS option key

This would be a very similar change to 023b874

[jsakamoto]

Doesn't the macOS option key work as ModKeys.Alt?

I'm not sure because I don't have any macOS devices, but MDN Web Docs say it should be working as an altKey.

• https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/altKey

[jsakamoto]

Ah...

I found a thread in the "Stack overflow" site.

• https://stackoverflow.com/questions/57486612/keyboardevent-altkey-is-false-on-keydown-event

It turns out that Option+u was actually returning the character ¨ instead of u for the key attribute.

Just as a historical reason, this library's current implementation looks up the key property first before looking up the code property.

https://github.dev/jsakamoto/Toolbelt.Blazor.HotKeys/blob/cbbc1a72e670d9d58b4af2f02dcfd6f01c6a94dc/Toolbelt.Blazor.HotKeys/script.module.ts#L130-L135

I might have to rewrite the part of this library where the above link points.

(...But I don't have any macOS devices... I have to go to Apple Store first!? 😅)

[bradystroud]

Hi @jsakamoto,

It seems like NativeCode always shows the correct character, so yes, it looks like https://github.com/jsakamoto/Toolbelt.Blazor.HotKeys/blob/master/Toolbelt.Blazor.HotKeys/script.module.ts#L130-L134 will need to be rewritten to use code primarily 😢

[jsakamoto]

@bradystroud
I fixed it at commit d803418fd9e6b7ff5516eb7700ae2a17f5acc444 !

(I used https://www.lambdatest.com/ to test it.)

Could you try out the latest version of the "Blazor Hotkeys" NuGet package?

• https://www.nuget.org/packages/Toolbelt.Blazor.HotKeys/11.1.1

[bradystroud]

(Closing issue) Hey @jsakamoto,

It works! 🙂 Thanks for that - Much appreciated