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
fix: keyCode
s being incorrectly converted in webContents.sendInputEvent()
#39776
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
codebytere
added
semver/patch
backwards-compatible bug fixes
target/25-x-y
PR should also be added to the "25-x-y" branch.
target/26-x-y
PR should also be added to the "26-x-y" branch.
target/27-x-y
PR should also be added to the "27-x-y" branch.
labels
Sep 7, 2023
codebytere
force-pushed
the
fix-input-event-parsing
branch
from
September 7, 2023 18:03
ea7d76a
to
1d6c8fc
Compare
VerteDinde
approved these changes
Sep 8, 2023
codebytere
force-pushed
the
fix-input-event-parsing
branch
from
September 11, 2023 07:35
1d6c8fc
to
2fd946e
Compare
codebytere
force-pushed
the
fix-input-event-parsing
branch
from
September 11, 2023 09:09
2fd946e
to
8146af1
Compare
Release Notes Persisted
|
I have automatically backported this PR to "25-x-y", please check out #39820 |
trop
bot
added
in-flight/25-x-y
and removed
target/25-x-y
PR should also be added to the "25-x-y" branch.
labels
Sep 12, 2023
I have automatically backported this PR to "26-x-y", please check out #39821 |
I have automatically backported this PR to "27-x-y", please check out #39822 |
trop
bot
added
in-flight/26-x-y
in-flight/27-x-y
merged/26-x-y
PR was merged to the "26-x-y" branch.
and removed
target/26-x-y
PR should also be added to the "26-x-y" branch.
target/27-x-y
PR should also be added to the "27-x-y" branch.
labels
Sep 12, 2023
trop
bot
added
merged/27-x-y
PR was merged to the "27-x-y" branch.
merged/25-x-y
PR was merged to the "25-x-y" branch.
and removed
in-flight/26-x-y
in-flight/27-x-y
in-flight/25-x-y
labels
Sep 12, 2023
MrHuangJser
pushed a commit
to MrHuangJser/electron
that referenced
this pull request
Dec 11, 2023
…Event()` (electron#39776) fix: sendInputEvent keyCodes being incorrectly converted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
merged/25-x-y
PR was merged to the "25-x-y" branch.
merged/26-x-y
PR was merged to the "26-x-y" branch.
merged/27-x-y
PR was merged to the "27-x-y" branch.
semver/patch
backwards-compatible bug fixes
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Closes #39610.
Fixed an issue where accelerators representing DOM keys were not correctly converted in
webContents.sendInputEvent()
. This was happening because our internal conversion logic was correctly parsing strings their respectiveui::KeyboardCode
values, but then failing to check whether the DOM code represented a standalone valid character. This led to an issue where a call to, for example,w.webContents.sendInputEvent({ keyCode: 'Plus', type: 'char' })
would get truncated and then sent to the input as the char string and not the dom key character if one existed.Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where accelerators representing DOM keys were not correctly converted in
webContents.sendInputEvent()
.