Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard emulation is not perfect #777

Closed
2 tasks done
aslushnikov opened this issue Sep 14, 2017 · 2 comments
Closed
2 tasks done

Keyboard emulation is not perfect #777

aslushnikov opened this issue Sep 14, 2017 · 2 comments
Assignees

Comments

@aslushnikov
Copy link
Contributor

aslushnikov commented Sep 14, 2017

Keyboard emulation is not perfect

aslushnikov pushed a commit that referenced this issue Oct 12, 2017
This patch starts sending proper `.code` field with emulated keyboard events.

References #777.
@aslushnikov
Copy link
Contributor Author

For the record: event.location is merged upstream as crrev.com/509990

aslushnikov added a commit to aslushnikov/puppeteer that referenced this issue Oct 20, 2017
This roll includes the following important revisions:
- https://crrev.com/509990 - DevTools: Allow location to be specified in
  Input.dispatchKeyEvent
- https://crrev.com/509486 - DevTools: fix extra HTTP headers not sent
on browser navigation request

References puppeteer#877, references puppeteer#777
aslushnikov added a commit that referenced this issue Oct 20, 2017
This roll includes the following important revisions:
- https://crrev.com/509990 - DevTools: Allow location to be specified in
  Input.dispatchKeyEvent
- https://crrev.com/509486 - DevTools: fix extra HTTP headers not sent
on browser navigation request

References #877, references #777
scheib pushed a commit to scheib/chromium that referenced this issue Oct 20, 2017
Puppeteer issue: puppeteer/puppeteer#777

Bug: none
Change-Id: Ib823af902263c7993978498174348fff28b47e1e
Reviewed-on: https://chromium-review.googlesource.com/714280
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Cr-Commit-Position: refs/heads/master@{#509990}
JoelEinbinder added a commit that referenced this issue Oct 23, 2017
BREAKING CHANGE:

This patch lets key names be code in addition to key. When specifying a code, the proper text is generated assuming a standard US keyboard layout. e.g Digit5 -> "5" or "%" depending on Shift.

* location is now specified. #777

* Using unknown key names now throws an error. #723

* Typing newlines now correctly presses enter. #681
@aslushnikov
Copy link
Contributor Author

This is fixed now.

ithinkihaveacat pushed a commit to ithinkihaveacat/puppeteer that referenced this issue Oct 31, 2017
This patch starts sending proper `.code` field with emulated keyboard events.

References puppeteer#777.
ithinkihaveacat pushed a commit to ithinkihaveacat/puppeteer that referenced this issue Oct 31, 2017
This roll includes the following important revisions:
- https://crrev.com/509990 - DevTools: Allow location to be specified in
  Input.dispatchKeyEvent
- https://crrev.com/509486 - DevTools: fix extra HTTP headers not sent
on browser navigation request

References puppeteer#877, references puppeteer#777
ithinkihaveacat pushed a commit to ithinkihaveacat/puppeteer that referenced this issue Oct 31, 2017
BREAKING CHANGE:

This patch lets key names be code in addition to key. When specifying a code, the proper text is generated assuming a standard US keyboard layout. e.g Digit5 -> "5" or "%" depending on Shift.

* location is now specified. puppeteer#777

* Using unknown key names now throws an error. puppeteer#723

* Typing newlines now correctly presses enter. puppeteer#681
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants