-
Notifications
You must be signed in to change notification settings - Fork 29.7k
PointerDeviceKind and ui.PointerChange forwards-compatibility #97350
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
Conversation
|
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
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add comment for linter comments per style guide.
d038e1d to
05e8cb0
Compare
dkwingsmt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| return buttons == 0 ? kPrimaryButton : buttons; | ||
| case PointerDeviceKind.unknown: | ||
| // ignore: no_default_cases, to allow adding new device types to [PointerDeviceKind]. | ||
| default: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this temporary? if so please leave a todo here with a link to the issue where the work is happening
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(same in the others)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make it permanent? Because this enum is always subject to adding new options.
Or what if we just remove unknown, since that's what "unknown" is for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removing "unknown" seems fine to me, i don't really understand how "unknown" would ever get set in the first place
|
IF this change is temporary and there's a commitment to a timeline to removing it: test-exempt: temporary code to allow rolling |
…r#97350) * PointerDeviceKind and ui.PointerChange forwards-compatibility * Add link to trackpad gestures issue * Add TODO
Needed to prepare framework for engine changes to support trackpad gestures (flutter/engine#28571)
Pre-launch Checklist
///).