-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[CP-stable]Fix non-vd android platform view input event offsets #52987
[CP-stable]Fix non-vd android platform view input event offsets #52987
Conversation
Fixes flutter/flutter#146570, which tracks a regression from flutter#49268 regarding platform view inputs in some specific cases. This PR translates the input event location to be the same as the location we calculated before flutter#49268, returning to the previous behavior, while maintaining the input event's verified status (I checked this manually with the `InputManager`). Tested manually with the reproduction in the linked issue. [C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
@gmackall please fill out the PR description above, afterwards the release team will review this request. |
Hmm, odd that the formatting is wrong here but passed the check on the original pr. Also, |
I agree, FWIW I also ran into an issue where I did a CP and the formatter failed. |
1a948ed
into
flutter:flutter-3.22-candidate.0
This pull request is created by automatic cherry pick workflow
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.
Issue Link:
What is the link to the issue this cherry-pick is addressing?
flutter/flutter#146570
Changelog Description:
Explain this cherry pick in one line that is accessible to most Flutter developers. See best practices for examples
Fixes a case where platform view inputs would get mapped to the wrong location on Android.
Impact Description:
Incorrect input locations on non virtual display Android platform views when used inside a scrolling view.
Workaround:
No
Risk:
What is the risk level of this cherry-pick?
Test Coverage:
Are you confident that your fix is well-tested by automated tests?
Validation Steps:
What are the steps to validate that this fix works?
Repro steps are in flutter/flutter#146570