Sorry about the miscommunication with support.
We’re tracking this as a bug that’s ready to work on but it hasn’t been picked up yet. We’re going to see if we can get it into the next sprint.
It’s not clear what the solution is because what you’re seeing is the native behavior of the Android WebView component and there is no configuration or setting to change it.