Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

[Win32] Don't redispatch ShiftRight keydown event - #25882

Merged
dkwingsmt merged 6 commits into
flutter-team-archive:masterfrom
dkwingsmt:win32-dont-redispatch-rshift-down
May 3, 2021
Merged

dkwingsmt merged 6 commits into
flutter-team-archive:masterfrom
dkwingsmt:win32-dont-redispatch-rshift-down

Conversation

@dkwingsmt

@dkwingsmt dkwingsmt commented May 3, 2021 •

Copy link
Copy Markdown
Contributor

This PR makes Win32 stop redispatching ShiftRight keydown event even if the framework does not handle it.

This is a bandage-fix to flutter/flutter#81674. It has been found out that, if the ShiftRight keydown is redispatched, Win32 weirdly would not dispatch the following key up event. The root cause is unknown.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
  • I listed at least one issue that this PR fixes in the description above.
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt. See testing the engine for instructions on
    writing and running engine tests.
  • I updated/added relevant documentation (doc comments with ///).
  • I signed the CLA.
  • All existing and new tests are passing.
  • The reviewer has submitted any presubmit flakes in this PR using the engine presubmit flakes form before re-triggering the failure.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@flutter-dashboard

Copy link
Copy Markdown

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@dkwingsmt
dkwingsmt requested a review from gspencergoog May 3, 2021 11:03

@gspencergoog gspencergoog left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

32384589-a60f0e74-c078-11e7-9bc1-e5b5287aea9d

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Development

Successfully merging this pull request may close these issues.

2 participants