Repository navigation
FocusableActionDetector should expose skipTraversal from Focus #187093
Description
FocusableActionDetector is currently missing a skipTraversal parameter, even though it internally uses a Focus widget that supports it.
At the moment, consumers of FocusableActionDetector cannot configure skipTraversal without reimplementing or copying the widget.
Example:
child: Focus(
focusNode: widget.focusNode,
autofocus: widget.autofocus,
descendantsAreFocusable: widget.descendantsAreFocusable,
descendantsAreTraversable: widget.descendantsAreTraversable,
canRequestFocus: _canRequestFocus,
onFocusChange: _handleFocusChange,
includeSemantics: widget.includeFocusSemantics,
skipTraversal: NO WIDGET.skipTraversal CURRENTLY,
child: widget.child,
),Focus already exposes skipTraversal, but FocusableActionDetector does not forward this property.
This becomes problematic for widgets that rely on keyboard navigation or custom traversal policies, because there is currently no way to opt in/out of traversal behavior while still using FocusableActionDetector.
Suggested solution:
Expose skipTraversal directly on FocusableActionDetector and forward it to the internal Focus widget.
Example:
const FocusableActionDetector({
super.key,
this.enabled = true,
this.focusNode,
this.autofocus = false,
this.descendantsAreFocusable = true,
this.descendantsAreTraversable = true,
this.skipTraversal,
...
});
final bool? skipTraversal;And:
skipTraversal: widget.skipTraversal,This would make FocusableActionDetector feature-complete relative to the underlying Focus widget and avoid requiring custom copies of framework code for a common focus configuration use case.
Activity
mbcorona commentedon May 27, 2026
Thanks for reporting @stan-at-work , routing as proposal to the framework team.
Expose skipTraversal in FocusableActionDetector
Expose skipTraversal in FocusableActionDetector (flutter#191308)
github-actions commentedon Sep 17, 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.