Recently ran into a conflict between what-input and another package I'm working with. Problem was that the components I'm using in the other package call e.preventDefault() internally, and so what-input would not switch from keyboard to mouse properly.
By listening to the capture phase, what-input can handle these events before they go down to the target.
Recently ran into a conflict between
what-input
and another package I'm working with. Problem was that the components I'm using in the other package calle.preventDefault()
internally, and sowhat-input
would not switch fromkeyboard
tomouse
properly.By listening to the capture phase,
what-input
can handle these events before they go down to the target.