jsakamoto

Thank you for your proposal! > ... take care of disposing the context. Oh, that is a good idea! 👍 I didn't come up with that. I'll consider implementing a...

@MisterGoodcat Thank you for that proposal! > Maybe we should have the option to let the JS part of your library force a blur? That might be a good idea,...

@Liero Thank you for your proposal! Your idea is interesting to me. I'll consider implementing this feature.

@NUlliiON Thank you for your comment! I already have an idea to implement this feature proposal, but unfortunately, I've not been able to get started yet... though after six months...

Wow, it sounds so cool! And, that's interesting! Yes, I'll consider supporting creating a browser extension scenario, particularly improve loading JavaScript helper code to be more flexible. But I'm afraid...

@newbe36524 I released the new version of "Blazor HotKeys", **ver.11.1.0**. - https://www.nuget.org/packages/Toolbelt.Blazor.HotKeys/11.1.0 I made this version to be able to disable automatic injection of the client-side script, instead of changing...

Thank you for your interesting proposal. I will consider implementing this idea, but it will take a long time to do it due to I have other libraries to maintain....

Unfortunately, it is impossible to disable keyboard shortcuts for contenteditable div at this time. Actually, I designed this library as a clone of the "angular-hotkeys" library, so I did not...

I released "Toolbelt.Blazor.HotKeys" ver.12.0.0 today. - https://www.nuget.org/packages/Toolbelt.Blazor.HotKeys/12.0.0 I added the "Exclude" flags for this version, and I deprecated the "AllowIn" flags instead. So if you want to disable a hotkey...

@wisniewskit Thank you for letting me know! This is my fault for the lack of E2E testing on Firefox. I published the fixed version of this library. - https://www.nuget.org/packages/Toolbelt.Blazor.HeadElement/7.2.1-preview.1#release-body-tab -...