TextInput with textAlign='right' inside a ScrollView gets focused on scroll (Android only)

[mmazzarolo]

Description

Hello there,
I've found a small issue on Android.
When a TextInput with has textAlign: 'right' inside a ScrollView and you press on it for scrolling it will focus instead (only on Android).
The correct behaviour would be to get focused only if you tap on it (without scrolling).
It works perfectly on iOS or if you remove the textAlign style.

EDIT: I'm having the same issue with textAlign: 'center'.
Works correctly with every other prop (left, justify, auto).

Reproduction

You can test it easily:

<ScrollView>
  <TextInput style={{ textAlign: 'right' }} />
  <View style={{ height: 2000 }} />
</ScrollView>

Additional Information

• React Native version: 0.40
• Platform: Android (tested on an emulated Nexus 5 and on real Moto G3)
• Operating System: MacOS

[hopha95]

I just tested with react-native 0.40.0 and cannot reproduce the problem. Which Android version are you running in your devices?

[mmazzarolo]

That's weird. Are you starting the scroll by tapping the textinput?
Also, is that a blank project?
I'm on 5.1.0.

Oh, and thank you for trying it man!

[hopha95]

Yes, this is a blank project. I'm starting outside of the TextInput. If you tap the text input then it should be focused, so I think this might not be an issue.

[mmazzarolo]

Ah-ha, there it is!
Nope, it should not be focused because:

1. If you remove the textAlign prop it doesn't get focused
2. On iOS it doesn't get focused
3. On many different native apps I tried it doesn't get focused (for example try the form in the new contact screen in Android)

Thank you anyway :)

[hopha95]

You're right, I tried and saw the problem. The textAlign caused the text input to be focused on touch.

[AndyJinSS]

I have the same problem on react-native 0.45.1

[igofind]

+1
No one can solve this problem?

[yangthen]

+1
multiline={true}
keyboardType={"default"}
and limit the maxLength can solve this problem temporarily @igofind

[turlac]

+1
@pecopeco just made my day. thank you for the workaround!
Any idea how we can get around the keyboard limitation of it having to be 'default' and not 'numeric'?

[igofind]

@pecopeco
Thanks ! It works!

[kengjungwa]

@pecopeco works but NOT on keyboardType={"numeric"}

[ahmetacikgoz]

+1
Same issue!

[programmdesign]

@pecopeco: thanks for the workaround. We can't use multiline though. Any idea for a workaround w/o multilines?