TextInput doesn't change focus on touch

[maxsmalls]

Hello, I'm wondering if I'm missing some simple setting or if I need to write my own controller to handle touch focus eventing.

When I have 3 text input fields on the screen, everything works as expected on the PC. By this I mean if I click one box with mouse, it has focus... I type some info into the box and without hitting enter on the keyboard click another text input... this works fine, only the new box has data entered.

If I build and deploy the actual app to the tablet, I get an issue. If I type in the first box, and I don't dismiss the keyboard, and tap a second box, both boxes get focus and anything I type goes into both. I can probably write a custom event or something to disable the first box if another one has focus, but figured I should check if this was accounted for.

Here's a video I recorded to show the problem.
https://youtu.be/fE3C5zaBPlE

Here's a quick snapshot of one of the textInput fields so you can see how it's currently configured:

Update 1: I've been doing some digging in the Text Field Mobile Input script and the Text Field script and the only thing I see that handles my situation is the case where the keyboard already exists when the control gains focus but I don't see anything about another window taking focus. In that event it just logs to the console if the keyboard was already present when the event went active so maybe I'm missing something somewhere else?

Update 2: I was able to deploy a debug build to the tablet and attach the vis studio debugger. It appears that HandleFocusLost() event is only getting called on these objects when the virtual keyboard enter key is pressed. I don't see the event trigger at all when I tap the other box but I see it called twice when pressing the done key.

[dkonik]

It looks like you discovered a bug in the current implementation of the TextField system on mobile, so you're not missing anything! We have a fix for this, and it will be included in our next release. We'll follow up here when it's published!

[maxsmalls]

Nice! I appreciate it! I did also come up with a temporary hack of my own but definitely would rather use your fix. :) Let me know if you want me to pull your feature branch to validate. I'm an automated tester in my day job as well so am familiar with software dev processes.

[adgray1]

The fix for this has just been published in Nova v2.1.0!