HTML form
Completing the HTML tab

Field

Description

Select to eliminate extra space characters in the processed HTML. This option can make transmission or processing more efficient; it does not alter the appearance of the HTML when displayed by Internet Explorer.

When selected, during stream processing the system:

• Deletes control characters such as tab and newline.
• Replaces two or more consecutive space characters with a single space, except within the curly brace characters that define a directive.

Stream processing copies space characters within the text of a property value and non-breaking spaces ( ) into the processed HTML without change.

Typically, the system sets this field to HTML or JSP, to indicate whether the HTML source is to contain HTML directives or JSP tags. For new controls, the initial value is JSP.

Use of JSP tags offers superior performance and other advantages over directives. Although both directives and JSP tags are supported, JSP tags are recommended for new development.

If this rule is circumstance-qualified or time-qualified, make this Generate For value match the Generate For value of the base rule. The base rule and the qualified rules must all use JSP tags or all use directives.

Do not save the rule form if you have composed HTML that contains both JSP tags and directives.

Indicates which browser types can to display the JSP or HTML from this rule. Note that PRPC does not validate your code. You must ensure that your code can be displayed across the supported browser types, which include Internet Explorer 7+, Firefox 3.5+, Safari 4+, and Chrome 5+.

The Browser Compatibility Report checks this value when determining what percentage of the rules in your application provide cross-browser support.

Select On to indicate that you have designed and implemented your HTML to meet your accessibility requirements.

The Accessibility Report evaluates this field on each rule in an application that displays it, when calculating application accessibility compliance levels. See Using the Accessibility report.

Enter source HTML directly in the HTML Source text area. Alternatively, click the pencil icon () to open an HTML editor. You can use JSP tags or directives in the source HTML you enter.

Use of JSP tags in HTML rules offers superior performance and other advantages over directives. Although both directives and JSP tags are supported, as a best practice use JSP tags in new application development.
Conversion of existing HTML rules that use directives to functionally equivalent rules that use JSP tags is straightforward. See Converting from directives to JavaServer Page tags.

When you finish entering HTML, close the editor. PRPC copies the HTML from a temporary file on your workstation into the HTML Source text area.

When using JSP tags, update the Pages & Classes tab to include each page name referenced in the HTML code, and identify the class of each page.

Use the <% and %> delimiters to surround an inline Java scriptlet within the HTML source code.

This button appears only after you save the form when the Generate For value is HTML and this rule is created by a Save As operation. See Converting from directives to JavaServer Page tags.

Reserved; do not use. Supports the Desktop API display.