XMLSCREENFIELD and NOXMLSCREENFIELD (JANUS DEFINE parameters): Difference between revisions
m (misc cleanup) |
mNo edit summary |
||
| Line 21: | Line 21: | ||
==See also== | ==See also== | ||
<ul> | <ul> | ||
<li>[[List of Janus commands]] | <li>[[List of Janus commands]] </li> | ||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | <li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] </li> | ||
</ul> | </ul> | ||
[[Category:JANUS DEFINE parameters|XMLSCREENFIELD and NOXMLSCREENFIELD]] | [[Category:JANUS DEFINE parameters|XMLSCREENFIELD and NOXMLSCREENFIELD]] | ||
Latest revision as of 16:44, 24 April 2015
Add or don't add screenField attributes to legacy screen XHTML
XMLSCREENFIELD and NOXMLCREENFIELD are parameters on JANUS DEFINE that indicate whether or not Janus Web Legacy Support adds screenField attributes to the 3270 screen content it converts to XHTML.
NOXMLSCREENFIELD, the default, indicates that screenField attributes are not added.
XMLSCREENFIELD specifies that:
- For input fields, the screenField atribute is added to the <input> element.
- For non-input fields, the screenField attribute is added to an extra <span> element that is placed around the displayed value.
Note: The XMLSCREEN and NOXMLSCREEN parameters indicate whether the output format of 3270 screens that Janus Web Legacy Support converts is XML or XHTML, respectively. If XMLSCREEN is specified, screen field names are always sent, making XMLSCREENFIELD irrelevant. XMLSCREENFIELD only affects screens sent as XHTML, which is only the case when NOXMLSCREEN is set.
The XMLSCREENFIELD and NOXMLSCREENFIELD parameters are available in Sirius Mods Version 8.1 and later.
You can override the XMLSCREENFIELD and NOXMLSCREENFIELD parameters on the JANUS DEFINE command on a URL basis using the like-named parameters in JANUS WEB SCREEN rules.
Valid only for WEBSERV ports.