HTML Tags for Mobile Device Interfaces

The mobile UI uses the following HTML tags:

Tag

Valid Values/Detail

type

Valid values are: text, hidden, or button.

subtype

Text type tags use the following values:
  • Label - Static text.
  • ProtectedText - Non-editable input.
  • Text - Input text box.

Hidden type tags use the value Hidden.

Button type tags use the following values:
  • Command - HTML button.
  • CommandLogout - Logs the user out and displays the login prompt.
  • CommandBack - Switches to the previous view.
  • CommandNextView - Switches to the next view.

name

Name of the field. Cannot contain spaces.

value

Value of the field (Internationalized string from the resource bundle)

size

Length of the field.

maxlen

Maximum length of the field.

row

Row in which the field should appear.

col

Column in which the field should start.

validate

Input data validated by the server. Valid values are:
  • Always - validate input data in all cases.
  • True - validate input data only if the old value if different from the new value.
  • False - do not validate input data.

mandatory

Field usage validated by the server. Valid values are:
  • True - the user is required to specify a value for the field.
  • False - the user is not required to specify a value for the field.

inputbinding

XML binding for a field. The UI infrastructure resolves this binding and displays the value on the UI.

outputbinding

XML binding for a field when the field value passes to the next screen.

tag

Binding for the field recognized by the UI infrastructure for Pocket PC and WinCE applications. The purpose of this is same as the outputbinding. The tag syntax is "binding=x", where 'x' is an XML binding (similar to the ones in Console screens).

defaultoutput

If this is not set to False, when inputbinding is resolved as void, the UI infrastructure resolves outputbinding of a field, and displays its value in the UI.

url

Specified only for "button/Command" field type/subtype. If set, the request is forwarded to the value of this attribute. It should always be of the form
target + "?action=" + calledFormName
where target is the value of the attribute target in the "form" element of the HMTL while calledFormName is the name of the JSP to be invoked without the ".jsp" extension.
Note: The sequence in which the UI infrastructure resolves an input tag is as follows:
  1. Resolves inputbinding.
  2. Resolves outputbinding if defaultoutput is not set to False.
  3. If no resolution is found, uses the value attribute provided in the HTML.
  4. If no resolution is found, uses the defaultvalue attribute provided in the HTML.
  5. Resolves defaultbinding.