Repository navigation
AX information on Android does not appear to account for device pixel ratio #7205
Description
Discovered this when using an internal AX inspection tool:
e.g. go/hsv/5051009483145216?node=11#
(Note the displayed layout is ~1/3rd the expected size.
@Hixie suggests @abarth might have broken this when moving the boundary between logical and physical around?
I haven't yet tested on a real device, so this may be a red herring.
Activity
Hixie commentedon May 13, 2017
I have this fixed on the framework side but it revealed a matching bug on the Java side whereby we are not properly scaling the positions (though we do scale the sizes correctly, interestingly). I haven't figured out what's going on there. The data is fine, since the touch-exploration feature is hit-testing correctly...
eseidelGoogle commentedon May 13, 2017
@jason-simmons is probably the person who knows our Android java code the best.
Fix a11y an Android (#3694)
github-actions commentedon Aug 17, 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.Fix a11y an Android (flutter-team-archive/engine#3694)