Repository navigation
showOnScreen should only scroll if new offset is within bounds #11665
Description
In accessibility mode, if showOnScreen [1] calculates an offset that is outside of the minExtent and maxExtent of the scrollable, we still attempt to scroll. This results in an overscroll animation, which is misplaced in a11y mode. Instead, if scrolling is not possible, nothing should happen.
Related: #11663
[1]
Activity
[-]showOnScreen should only scroll if new offset is within bounds[/-][+]a11y scrilling should only scroll if new offset is within bounds[/+][-]a11y scrilling should only scroll if new offset is within bounds[/-][+]showOnScreen should only scroll if new offset is within bounds[/+]goderbauer commentedon Dec 20, 2017
Related: #12274
goderbauer commentedon May 18, 2018
This is an issue for Tables that scroll in x and y direction.
jonahwilliams commentedon Jul 17, 2018
@goderbauer should this behavior only be implemented in a11y mode?
goderbauer commentedon Jul 17, 2018
I believe this needs to be fixed regardless of a11y mode.
5 remaining items
jonahwilliams commentedon Oct 8, 2018
One possible fix is to inject a non-bouncing scroll physics when MediaQueryData.accessibleNavigation is enabled.
TahaTesser commentedon Sep 8, 2020
Is this issue still valid?
flutter/packages/flutter/lib/src/widgets/single_child_scroll_view.dart
Lines 664 to 677 in f9fd71b
goderbauer commentedon Sep 8, 2020
/cc @LongCatIsLooong Did one of your fixes in this area address this by any chance?
LongCatIsLooong commentedon Sep 8, 2020
I think that fix only affects persistent headers, so unlikely.
flutter-triage-bot commentedon Oct 30, 2026
This issue is assigned to @mbcorona but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!