Dynamic Elements Changes

All dynamic elements now define an otherTagString attribute. Use this attribute to include a string directly in the element's HTML tag. Some HTML elements contain parameters that are not key-value pairs. If you wish to include one of these parameters in your element, you can send it using this attribute.
Every element which supports the displayString binding now has an escapeHTML attribute. For the following elements, escapeHTML defaults to YES:
WOBrowser
WOPopUpButton

For these following elements, escapeHTML defaults to YES if you use the displayString binding, and NO if you use the (now deprecated) value binding:

WOCheckBoxList
WORadioButtonList
WONestedList
Two new dynamic elements have been added to the WebObjects framework to better support JavaScript. They are called WOActionURL, which is similar to WOHyperlink; and WOResourceURL, which is similar to WOImage.
WOPopUpButton and WOBrowser have a new selectedValues attribute which passes the selected objects to a popup or browser via a list of selected values rather than a list of selected objects. The selected values come directly from the form values of the request.
The first item in a WOPopUpButton can now be an empty selection. Bind the noSelectionString attribute to a string that, if chosen, represents an empty selection. If the user leaves the WOPopUpButton at this item, then the selection attribute is set to null or nil.
WOTextField and WOString have a new attribute, formatter, which should be bound to an NSFormatter instance. In the event a user enters a value that cannot be formatted, these elements will pass the invalid value through, allowing you to send back an error page that shows the invalid value. Note that the prior behavior in this case was to pass back a blank value for the field.
The behavior of WORadioButton and WOCheckBox changed slightly so that they now push NSNumber objects with a value of 1 or 0 rather than @"1" or nil (null in Java) to indicate the state of the button or check box. The old behavior still applies if WebObjects 3.5 request handling is enabled (see Troubleshooting WebObjects 4.0 Request Handling).

Table of Contents Next Section