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
showOnScreen / getOffsetToReveal doesn't take status bar into consideration #11663
This is a problem for a11y. When an item is partly covered by the status bar and a11y focus is moved to it, Android issues a showOnScreen action, which is handled by [1]. It will currently calculate via [2] that the item needs to be aligned with the upper edge of the screen. This is incorrect. It should be aligned with the lower edge of the status bar.
While this sounds like just a visual annoyance, it can actually cause a11y users to get stuck: When the list is scrolled all the way to the bottom, the showOnScreen action should scroll it down a little. Instead, we currently try to scroll up, but that's not possible as we are already at the end. The user needs to resort to two finger scrolling to get out of this situation.
We should probably make the "scroll into view" logic optionally take a rect that describes the "view". Then the accessibility code could just exclude any system-level padding when giving it the instruction to scroll.
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
Hixie commentedon Aug 17, 2017
We should probably make the "scroll into view" logic optionally take a rect that describes the "view". Then the accessibility code could just exclude any system-level padding when giving it the instruction to scroll.
github-actions commentedon Aug 15, 2021
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.