!--a11y-->
InputField 
The InputField UI element allows the user to edit or display a single-line text. With an InputField, you can edit any simple data type you like. The conversion from the internal display format and, when the user has input a value, back into the internal display format is done automatically. If, after the user has input a value into the field, an error occurs during the conversion to the internal format, the value is not put back into the context, but remains in the data container. When it is next displayed, the InputField with the erroneous value is bordered in red and displayed with an error message.
The input is not checked until the roundtrip is triggered.

To enable the
development of
accessible
applications, the label property is checked during the syntax
check.
If no label has been set, and no descriptive text has been specified for the appropriate bound context element in the ABAP Dictionary, the tooltip property is checked.

Note that the value of InputField is also transferred to the password mode in plain text. For this reason, applications that use the passwordField property should only run in HTTPS mode.
You can go to the HTTPS mode through an ICF service setting in transaction SICF by setting SSL for Security Requirement on the Logon Data tab on the node for your application in the HTTP service tree.
More information:
Example of the Display with a Label
|
|
Runtime Class |
CL_WD_INPUT_FIELD |
Properties in View Designer
Name |
Type |
Initial Value |
Bindable |
ID |
STRING |
(automatic) |
No |
WDUI_INPUT_FIELD_ALIGNMENT |
auto |
Yes |
|
WDY_BOOLEAN |
true |
Yes |
|
Text |
|
No |
|
WDUI_IMEMODE |
auto |
Yes |
|
I |
0 |
Yes |
|
WDY_BOOLEAN |
false |
Yes |
|
WDY_BOOLEAN |
false |
Yes |
|
WDUI_STATE |
normal |
Yes |
|
WDUI_TEXT_DIRECTION |
inherit |
Yes |
|
Text |
|
Yes |
|
Text |
|
Mandatory |
|
WDUI_VISIBILITY |
visible |
Yes |
|
STRING |
|
Yes |
Events in View Designer
Name |

Other properties that can be inherited are defined in the associated higher-level classes. The associated UI elements are:
For dynamic programming, the same properties, events and aggregations are available as in the View Designer. Bear in mind the different spellings.
Dynamic Programming of Properties
View Designer Name |
Runtime Name |
Type |
ALIGNMENT |
WDUI_INPUT_FIELD_ALIGNMENT |
|
alignment: auto |
CL_WD_INPUT_FIELD=>E_ALIGNMENT-AUTO |
|
alignment: beginOfLine |
CL_WD_INPUT_FIELD=>E_ALIGNMENT-BEGIN_OF_LINE |
|
alignment: center |
CL_WD_INPUT_FIELD=>E_ALIGNMENT-CENTER |
|
alignment: endOfLine |
CL_WD_INPUT_FIELD=>E_ALIGNMENT-END_OF_LINE |
|
alignment: forcedLeft |
CL_WD_INPUT_FIELD=>E_ALIGNMENT-FORCED_LEFT |
|
alignment: forcedRight |
CL_WD_INPUT_FIELD=>E_ALIGNMENT-FORCED_RIGHT |
|
ENABLED |
WDY_BOOLEAN |
|
EXPLANATION |
WDY_MD_TRANSLATABLE_TEXT |
|
IME_MODE |
WDUI_IMEMODE |
|
imeMode: active |
CL_WD_INPUT_FIELD=>E_IME_MODE-ACTIVE |
|
imeMode: auto |
CL_WD_INPUT_FIELD=>E_IME_MODE-AUTO |
|
imeMode: disabled |
CL_WD_INPUT_FIELD=>E_IME_MODE-DISABLED |
|
imeMode: inactive |
CL_WD_INPUT_FIELD=>E_IME_MODE-INACTIVE |
|
LENGTH |
I |
|
PASSWORD_FIELD |
WDY_BOOLEAN |
|
READ_ONLY |
WDY_BOOLEAN |
|
STATE |
WDUI_STATE |
|
state: normal |
CL_WD_INPUT_FIELD=>E_STATE-NORMAL |
|
state: required |
CL_WD_INPUT_FIELD=>E_STATE-REQUIRED |
|
TEXT_DIRECTION |
WDUI_TEXT_DIRECTION |
|
textDirection: inherit |
CL_WD_INPUT_FIELD=>E_TEXT_DIRECTION-INHERIT |
|
textDirection: ltr |
CL_WD_INPUT_FIELD=>E_TEXT_DIRECTION-LTR |
|
textDirection: rtl |
CL_WD_INPUT_FIELD=>E_TEXT_DIRECTION-RTL |
|
TOOLTIP |
WDY_MD_TRANSLATABLE_TEXT |
|
VALUE |
WDY_MD_TRANSLATABLE_TEXT |
|
VISIBLE |
WDUI_VISIBILITY |
|
visible: none |
CL_WD_INPUT_FIELD=>E_VISIBLE-NONE |
|
visible: visible |
CL_WD_INPUT_FIELD=>E_VISIBLE-VISIBLE |
|
WIDTH |
STRING |
|
Dynamic Programming of Events
View Designer Name |
Runtime Name |
ON_ENTER |
You can find examples of this interface element in the system in the WDR_TEST_UI_ELEMENTS Web Dynpro application and in the WDR_TEST_EVENTS component in the InputField view.