You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
InkWell does not expose callbacks for handling tertiary taps #129058
In my app, I want to replicate the behavior of opening content in another view via the middle mouse button. I'm not quite sure if Material intends a ripple effect to be shown for the middle mouse button but in this case I thought to put it in my existing InkWell for now. I see that #62788 has implemented middle mouse button clicks (tertiary taps) but the PR author failed to update potentially related widgets.
Side note: I am slightly worried about the API complexity as it is right now because we're introducing 4 callbacks for each pointer device button. A drawing tablet stylus can have up to 3 buttons and a mouse up to 5 buttons. Are there any plans to refactor/simplify/future-proof these interfaces?
Hi @Craftplacer, I think given a specific widget and use-case we would welcome a PR to add tertiary tap support. I do recognize that this callback pattern doesn't scale well, and is definitely something that requires a re-visit in the future. One potential solution I can think of is providing the button type in the details object provided to a callback. If I find some time I'll explore this, but anyone is also welcome to try.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Craftplacer commentedon Jun 17, 2023
Side note: I am slightly worried about the API complexity as it is right now because we're introducing 4 callbacks for each pointer device button. A drawing tablet stylus can have up to 3 buttons and a mouse up to 5 buttons. Are there any plans to refactor/simplify/future-proof these interfaces?
darshankawar commentedon Jun 19, 2023
The said methods are exposed / available for GestureDetector class but not for InkWell currently.
https://api.flutter.dev/flutter/material/InkWell/InkWell.html
Craftplacer commentedon Jun 21, 2023
Related: #115641
HansMuller commentedon Jun 21, 2023
CC @Renzo-Olivares
flutter-triage-bot commentedon Mar 8, 2024
This issue is missing a priority label. Please set a priority label when adding the
triaged-designlabel.Renzo-Olivares commentedon Mar 19, 2024
Hi @Craftplacer, I think given a specific widget and use-case we would welcome a PR to add tertiary tap support. I do recognize that this callback pattern doesn't scale well, and is definitely something that requires a re-visit in the future. One potential solution I can think of is providing the button type in the details object provided to a callback. If I find some time I'll explore this, but anyone is also welcome to try.
Add tertiary tap callbacks to InkResponse and InkWell
Add tertiary tap callbacks to InkResponse and InkWell
[material_ui] Add tertiary tap callbacks to InkResponse and InkWell (f…
github-actions commentedon Oct 28, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.