Filter
Top Products
Forum.Nokia.com
<select name="country" multiple="true">
<option value="-">-</option>
<option value="Australia">Australia</option>
<option value="Canada" size="25">Canada</option>
<option value="Denmark">Denmark</option>
<option value="Finland">Finland</option>
<option value="France">France</option>
<option value="Germany">Germany</option>
<option value="Italy">Italy</option>
</select>
</p>
<do type="accept" label="Enter" optional="false">
<go href="#confirm" method="get" sendreferer="false"/>
</do>
<do type="prev" label="Back" optional="false">
<prev/>
</do>
</card>
</wml>
Example 5: Do element - options list items.
3.5.2 Prev type do elements
Whenever a new card is shown, a new history list item is created. When activating the prev task on a
WML card, the target URL is the previous history list item and the current card (in which prev was
activated) is not retained in the history list (there is no "forward" function).
Do elements of the type “prev” are handled as an exception to other types of do elements (see section
4.5.1). If there is only one "prev" type do element active, it is not shown on the options list. Instead, it
is bound to the 2
nd
CBA button and it is labelled as "Back". The 2
nd
CBA is dimmed if there is zero or
more than one "prev" type do element active and do elements are displayed on the options list like all
other do elements. It is likely that most pages implement only one do element of the type "prev".
The author of the WAP service is always responsible for the working navigation model within the
service. If there is a need for back functionality, it should be explicitly defined with the "prev" type do
element. The WAP browser does not have any implicit back functionality.
WAP Service Developer’s Guide for Nokia 9200 Communicator Series
17