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

feat: make keyboard.down generate input event by default #1016

Merged
merged 1 commit into from Oct 13, 2017

Conversation

JoelEinbinder
Copy link
Collaborator

Breaking change:
Except for in really strange circumstances, pressing the key a will generate an input event with the text 'a'. This patch makes it the default behavior in puppeteer.

#723

Copy link
Contributor

@aslushnikov aslushnikov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarification:

This patch addresses bullet n.2 of #723:

Explain the difference between keyboard.press('a') and keyboard.press('a', {text: 'a'}). Also, should there be a difference?

With this patch, there's no longer any difference.

@aslushnikov aslushnikov merged commit 6a8865c into puppeteer:master Oct 13, 2017
ithinkihaveacat pushed a commit to ithinkihaveacat/puppeteer that referenced this pull request Oct 31, 2017
…uppeteer#1016)

This patch starts generating input events for `keyboard.down`, addressing bullet 2 of
puppeteer#723. With this patch, there's no longer any difference between `keboard.press('a')` and
`keyboard.press('a', {text: 'a'})`.

BREAKING CHANGE:
`keyboard.down('a')` starts generating input event (wasn't the case before).

References puppeteer#723
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants