And another comment that comes to the "multiline" property.

When multiline is turned off the focus event scrolls to the input field.

When multiline is turned on the focus event doesn't scroll to the input field.

Further notes. Input fields are repeated with a list of objects. Inputs are the primitive input fields.

Another ping, Timo Kapanen, on this topic, however not directly about focusing a composite component.

Whenever I have a page layout as described here the focus input doesn't bring up the input field completely, only to half of it, see image below:

Page layout structure:

page- disabled scrolling, stretch to viewport height.

layout tree simplified:

>-container (set height to pixels)

>-scroll view (height set to "Grow to height")

>-container (height set to "fit content" (layout horizontal, etc)

>->-primitive input (grow to height, because it can in fact be a long text)

One thing to note that this is not an issue if I have a container above the input, but I need to let the user scroll and this issue happens on both scroll view and recycler view component. (I mean when any of these two are above my container with the input).

Oh and if we are already talking about the input issues. On android when an input is in focus the navigation bar is also moved on top of the keyboard. I am not sure if this is intended, but for my current use case it just causes overall problems in the UI.

This is how the input is brought up by on the focus input flow:

I'll add to this.

If you have set a component to visible then attempt to set focus to an input field that's inside a scroll view, it doesn't work.

Taking the input field out of the scroll view resolves this issue.