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
To ensure that the JS side matches the native side when declarative properties for handling specific keyboard keys are set, it would be good to implement preventDefault() on the JS side similar to how we marked handled() in the native side.
The bug is tracking adding some logic to the JS that says when a component gets the keydown event, it should call preventDefault if the component marked keyDownEvents for that key. And it shouldn't call it if the component didn't mark keyDownEvents. That way, the native and JS event propegation are in sync with each other. And in the future we can potentially make the key events happen synchronously and it wont be a behavior change.
rectified95
changed the title
Implement preventDefault() when keyboarding declarative properties are set
Implement event.stopPropagation() when keyboarding declarative properties are set
Apr 20, 2021
To ensure that the JS side matches the native side when declarative properties for handling specific keyboard keys are set, it would be good to implement
preventDefault()
on the JS side similar to how we marked handled() in the native side.See comment thread for details.
The text was updated successfully, but these errors were encountered: