Is your feature request related to a problem? Please describe.
Expect the BaseButton widget's onTapUp to maintain the same callback as GestureDetector's onTapUp.
Suggestion: It would be great if BaseButton's onTapUp callback could behave the same way as GestureDetector's onTapUp (e.g., in IconButton, FilledButton, etc.).
Reason: In some complex scenarios, I need to access the user's tap position, and retrieving it from onTapUp would be very convenient—just like how GestureDetector currently works.
While it's possible to wrap a button with GestureDetector as a workaround, this approach introduces issues such as:
Event priority conflicts (tap handling order).
Loss of hover effects when using IgnorePointer to manage event propagation.
Other frustrating edge cases.
Having consistent onTapUp behavior across buttons would greatly improve usability.
Since changing the existing behavior might introduce breaking changes, we could alternatively add a new method like rawOnTapUp to preserve backward compatibility.
Is your feature request related to a problem? Please describe.
Expect the BaseButton widget's onTapUp to maintain the same callback as GestureDetector's onTapUp.
Suggestion: It would be great if BaseButton's onTapUp callback could behave the same way as GestureDetector's onTapUp (e.g., in IconButton, FilledButton, etc.).
Reason: In some complex scenarios, I need to access the user's tap position, and retrieving it from onTapUp would be very convenient—just like how GestureDetector currently works.
While it's possible to wrap a button with GestureDetector as a workaround, this approach introduces issues such as:
Event priority conflicts (tap handling order).
Loss of hover effects when using IgnorePointer to manage event propagation.
Other frustrating edge cases.
Having consistent onTapUp behavior across buttons would greatly improve usability.
Since changing the existing behavior might introduce breaking changes, we could alternatively add a new method like rawOnTapUp to preserve backward compatibility.