Android back button can conflict with select widget mode magnifying glass

[helin24]

During a user interview yesterday, a user was having trouble toggling select widget mode using the magnifying glass in an Android emulator because clicking it hit the android back button instead. I'm not sure if this was due to a specific emulator device; can put you in touch with the user if you need more info. cc @jacob314

[polina-c]

Helin, it is not clear what relates to Android emulator and what relates to DevTools. Can you please provide detailed steps to repro?

[helin24]

I'll connect you with the user

[kenzieschmoll]

Sounds like this is an issue with the FAB that appears on an app when Select Widget Mode is enabled:

This screenshot is from an iOS Simulator, but an android emulator will have the Android back button just below this FAB.

In the short term, we could consider making the FAB larger or adding more padding between the button and the edge of the screen.

CC @InMatrix - another issue suggesting we should come up with a better design for this workflow.

Related #3567

[yvonnejiang]

Hello, I'm the user Helin was talking to previously, attached is a video of my use case. It's a little hard to see, but in the video, tapping in the direct center of the magnifying glass widget inspector button ends up triggering the system nav back button instead, when the Android device is using 2 or 3 button navigation instead of gesture nav. At the very end of the video I show the case where if the button is tapped at the very top edge, it actually handles the tap correctly, but the target area where this works is quite small, apparently.

It may be worth noting that this only started happening after setting the setEnabledSystemUIMode to "edgeToEdge". Without edgeToEdge, taps register on the button perfectly fine.

inspector-edge-to-edge.mp4

[github-actions]

Without additional information we're not able to resolve this issue, so it will be closed at this time. You're still free to add more info and respond to any questions above, though. We'll reopen the case if you do. Thanks for your contribution!

[CoderDake]

Our workflows erroneously closed this. Re-opening it.