Use with specific DOM element, don't attach to window about keymage

[piranha]

Can I ask you what's the usecase for that? Because there is scope (namespacing) support for the case when you want to enable/disable shortcuts in cases like popup is shown or something like that.

Thing is that binding on element receives keys only when focus on an element or any of it's children, which is often not the case. But I'm open for discussion. :)

[orbitbot]

The idea would be to only capture keypresses when an element is focused, rather than globally. In my usecase, I have implemented a lightweight library for IDE-like behaviour for contenteditable html tags: https://orbitbot.github.io/misbehave/ , and keymage should probably be able to handle my needs for that project (with the filed issues fixed) while cutting the unminified size of misbehave in half.

Instantiation with a target element would enable 1) easier use without needing to bother with global scopes for keymage, 2) multiple simultaneous instances that do not interfere with each other (such as needing to figure out which element the event was fired on etc.)

[piranha]

Oh, right, with contenteditable it would work this way.

As for figuring it out - you don't usually need that, you just catch focus on that element and set/unset scope.

But I'll think what's the best way to bind to a concrete element. Don't want to change API much. :)

[piranha]

So yeah, if anybody wants to implement that - I would consider taking a patch, but I see no real need for it.