TextEdit style attributes

Textedit presentation style attributes apply to the TEXTEDIT element.

Note: This topic lists presentation style attributes for a specific class of form element, common presentation style attributes can also be used for this type of element.
Table 1. TextEdit style attributes

Defines if the textedit field allows search facility (Control-F).

Values can be "yes" or "no" (default).

Yes No No No

By default, to avoid "Stored XSS" attacks, the front-end cleans the HTML sent to form elements to ensure no malicious script can be executed. This security control prevents for example to use HTML content such as "<a href='mailto: …". The default for the sanitize attribute is "yes". To disable the checking of HTML content send to form elements, set the sanitize style attribute to "no".

No Yes No No

Defines if the toolbox for rich text editing is shown or not.

Possible values are "auto"(default), "yes", "no".

Only available if textFormat style attribute is set to "html".

Yes Yes No No

Defines if the textedit field includes a spelling checker.

  • With GDC, the possible values are the two dictionary files needed for each language (one .aff and one .dic). These files can be downloaded here. Only the files available for OpenOffice.org 2.x are working (files for OpenOffice.org 3.x are not supported yet):

    Supported file formats are:
    • Simple relative locale files like "my_affix_file.aff|my_dictionnary_file.dic"
    • Absolute paths such as "file:///c:/dics/my_dictionnary_file.aff|file:///c:/dics/my_dictionnary_file.dic"
    • URLs such as http://mywebserver.com/my_affix_file.aff|http://mywebserver.com/my_dictionnary_file.dic

    The local directory of dictionary files can be queried in the GDC with the standard.feInfo front call using the dictionariesDirectory parameter

  • With GBC, the attribute is not applicable: Input fields use the web browser spellchecker.

  • With GMI, available values are "yes" or "no". If this attribute is not set, iOS will decide if spell checking is enabled, depending on the global auto-correction setting on the device.

Yes (see note) No (see note) No Yes (see note)

Defines the rendering of the content of the widget.

Values can be:
  • "plain" (default): the value assigned to this widget is interpreted as plain text.
  • "html", the value is interpreted as HTML (with hyperlinks), with rich text input feature enabled.
    Important: The HTML content displayed inside a form element using the textFormat:html style must not be a complete HTML document (using CSS styles for example). The content must be simple HTML, with basic tags such as text decoration like <b/> for bold, <ul/>+<li/> for bullet lists, and inline styles.
    Note: Consider using the fglrichtext web component, instead of the rich text option in TEXTEDIT fields.

    For more details, see Rich Text Editing in TEXTEDIT.

Yes Yes No No

Defines where the text can be wrapped in word wrap mode.

Values can be:
  • "atWordBoundary" (default): the text will wrap at word boundaries.
  • "anywhere": the text breaks anywhere, splitting words if needed.
Yes Yes No No