HTML TextInput UX issues

[etoledom]

This is a follow up of many UX issues regarding the HTML editor.

As an alternative of using InputView, we could try to use Aztec component on HTML edit mode. It might save us some troubles (or add more?)

Both platforms:

• When there is more than one screen of text, and the user scrolls the content, it will always start editing showing the keyboard.

Android:

• When it first appear, It is shown scrolled to the bottom.
• On focus, it will always scroll to the bottom and show the cursor at the end.
• When is empty, the cursor is at the middle of the screen. Add textAlignVertical to html text input. #114

iOS

• When there's more than one screen of text, adding text will automatically jump the cursor to the top of the screen. Fix jumpy html text input on iOS #115

[daniloercoli]

On focus, it will always scroll to the bottom and show the cursor at the end.

This is an ugly problem IMO, especially when you switch to HTML to be able to edit a long post (with maybe unsupported blocks). You scroll the view until you find the part of the text you want to modify, and then tap on the screen....It took a while to figure out where to put back the caret.

[etoledom]

I like the idea of using the HTML Editor used on Aztec. Hopefully that will solve these problems 🙏

[SergioEstevao]

@hypest should we try to fix the issues above or move to the solution where we use the native HTML editors?

[hypest]

I'd favor using a native-based html editor (Aztec's can be an option), thinking that since html mode is a long string of rich-text content (think: syntax highlighted) it might not be very performant to rely on RN/JS for the editing UX.