You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very similar to #56, if two <Shortcut /> tags with the global prop are rendered, one as the child of the other, and they both bind to the same keys, the parent's handler is called before the childs. This is despite the child <Shortcut /> tag being closer to the event target.
IMHO, this is not what people will expect. Users of react and front event developers are accustomed to event handlers defined closer to the target of an event being called first (and being given the chance to stop that event from propagating to handlers attached to parent elements).
The text was updated successfully, but these errors were encountered:
Very similar to #56, if two
<Shortcut />
tags with theglobal
prop are rendered, one as the child of the other, and they both bind to the same keys, the parent's handler is called before the childs. This is despite the child<Shortcut />
tag being closer to the event target.IMHO, this is not what people will expect. Users of
react
and front event developers are accustomed to event handlers defined closer to the target of an event being called first (and being given the chance to stop that event from propagating to handlers attached to parent elements).The text was updated successfully, but these errors were encountered: