It's actually up to the input method app, not the Android framework itself, to decide what to do with the values you set.
The Android framework just passes the values you set through to the input method, which can then choose what buttons to show on the keyboard or an "extracted" EditText
in full-screen view. The Android framework influences the EditorInfo
in two ways:-
It passes it through
EditorInfo.makeCompatible
to ensure the values therein are compatible between the keyboard's and the app'stargetApiVersion
s. At the moment this only affects someInputType
values, not the editor action, but this could change if new editor actions (or completely new settings) are introduced.It sets the default behaviour for the input method, including the behaviour around full-screen editors. If the input method chooses not to override this default behaviour, then it could end up with behaviour that's different between Android versions. Many keyboards do choose to set their own behaviour, in a way that's consistent between Android versions.
For that reason, it's not so simple to say that a certain EditorInfo
field has a certain effect on any given version, and there's no way to ensure a consistent behaviour, even on one Android version. All you're doing is providing hints to the input method, which chooses how to present them to the user.