TextInput's autoCapitalize changes inputType unexpectily. This is not mentioned in the docs.

[voxlz]

Description

TextInput's autoCapitalize changes inputType unexpectily. This is not mentioned in the docs.

What is the problem?

I just spent an hour debugging why I'm losing certain keystrokes on android. It turns out that using the autoCapitalize flag will change the text input after the first input, casing a short period where inputs are not registered. This is quite unexpected and not really meantioned in the docs.

How can we address it?

Update the list of unsupported inputTypes to include the android only "visible-password", and add a description what happenes if do use them together (it will switch over to a supported inputType it seems)

Why is it important?

This is quite unexpected and will save time debugging.

Who needs this?

People who like me are trying to hide auto sugesstions will be forced to use "visible-password". I think it's good to explicity warn those developers against using autoCapitalize.

When should this happen (use version numbers if needed)?

I don't really know.

[voxlz]

           <TextInput
              keyboardType="visible-password"
              autoCapitalize="words"
           />

vs

           <TextInput
              keyboardType="visible-password"
           />

[github-actions]

👋 Hey there, it looks like there has been no activity on this issue in the last 90 days. Has the issue been fixed, or does it still require the community attention? This issue will be closed in the next 7 days if no further activity occurs. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.