IssueTracker

Currently, cursor behaves like this: it starts blinking when the field in focus and TextValue is not empty. In most cases this is normal, but there are some special cases where this is not the case. For example, we have a TV screen with an input field and an on-screen keyboard (see attachment file). Here, when you move focus from the input field to the keyboard, you still have the ability to move the cursor using the arrow keys on the keyboard, but the cursor must be visible. This case does not violate the logic of the input system: we still have one input target. But when there is more than one input field on the screen, the cursor behavior should not change. I suppose we can add a parameter to BasicTextField, which will make the cursor visibility behavior more flexible.

@Composable
BasicTextField(..., cursorVisibility: CursorVisibility = WHILE_FOCUSED, ...)

...

enum class CursorVisibility{
    WHILE_FOCUSED, // Current behavior
    ALWAYS, // Cursor always visible
    NEVER // Cursor never visible
}