Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

browserTrigger doesn't support keydown with a specific keycode #8688

Closed
jintoppy opened this issue Aug 20, 2014 · 2 comments
Closed

browserTrigger doesn't support keydown with a specific keycode #8688

jintoppy opened this issue Aug 20, 2014 · 2 comments

Comments

@jintoppy
Copy link

if I do browserTrigger(element, 'keydown'), there is no option to give keyCode. It is going to line 127, to initMouseEvent, even though this is a keydown event.

@caitp
Copy link
Contributor

caitp commented Aug 20, 2014

Personally I don't think this would be too bad, since it's not included in production code anyways --- my vote is PRs welcome.

@caitp caitp added this to the Backlog milestone Aug 20, 2014
@gonzaloruizdevilla
Copy link
Contributor

For PR #10193 I had to do exactly this.

I had to make two different commits:
gonzaloruizdevilla@2f0d4fb to allow key events
gonzaloruizdevilla@d70e0d4 to force artificially event bubbling in trees detached from the document (bubbling don't work in these cases in some browsers like chrome)

petebacondarwin added a commit that referenced this issue Jun 6, 2016
Support for key events like keypress, keyup or keydown.

Closes #8688
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants