Add TextEditor
core provider, rewrite TextInput
UI element on top of it
#8575
Milestone
TextEditor
core provider, rewrite TextInput
UI element on top of it
#8575
Similar to #8574, handling text input internationally is a painful task, and sometimes we do not even have a proper API to handle it, as text input is something strictly tied with the OS-backed TextEdit widget. (This is not just Kivy's case, but also other frameworks are on the same boat).
The current status:
The window provider (SDL in most cases) does not have (and is not required to?) all the events and methods to access the complete feature set that the (mostly mobile) platforms offer.
We currently only support basic text input methods (we receive keystrokes from the keyboard and change the TextInput widget text property accordingly). This may be fine for languages that do not require an Input Method Editor (IME) to input text.
The window provider (SDL in that case) is not able to handle multiple TextInput fields at the same time. That breaks the keyboard suggestions for us.
The current implementation does not allow us to handle autofills (E.g. for password managers)
The current implementation does not allow us to handle accessibility features on textinputs.
We have a POC #8226, whose major intention was to test the feasibility of using OS-backed hidden widgets to get the events. That worked quite fine. We need to find out how to manage it for Desktop platforms, and write a unified API + keep the support for the legacy (keystrokes) version.
Please note that this issue is partially on hold until #8574 is assessed, since
kivy.ui.textinput
will useTextLayout
core provider (for layouting, rendering, getting selection rectangles, getting glyph at cursor pos, ...) andTextEditor
core provider for handling the textedit events.Related issues to consider:
input_type
is set to "number" #8232TextInput
on android does not work withon_text_validate
method #8267The text was updated successfully, but these errors were encountered: