An anchored link associates a task with string of formatted text. You can specify a link anywhere in formatted text except on choice cards. When the user scrolls to a link, the phone displays the > marker next to it; the ACCEPT label changes to the label specified by the link (if any). If the user presses ACCEPT, the UP.Phone executes the task specified by the link.
A link can also specify a numeric key (0-9) as an accelerator key. The number of the accelerator key appears at the left side of the row containing the link. If the user presses the accelerator key at any time while the card containing the link is on the screen, the UP.Phone executes the task specified by the link.
Links have precedence over ACCEPT actions defined at the card and the deck level. For the complete rules of action precedence, see Action precedence for function keys.
| Statement | Description |
|---|---|
<A
| |
The label that appears on the ACCEPT key when the link is selected.
The | |
A number (0-9) that appears on the left side of the screen next to the link. If the user presses the corresponding key on the phone keypad, the phone executes the task defined by the link. It is recommended that you number the links in the order in which they appear. | |
The task to execute. Possible values are:
See the table below for more detailed descriptions of these tasks and the options you can use with them. | |
The URL to request in
If the current activity is nested and the task is a | |
Instructs the phone to prefetch the URL specified by the If the user invokes the action (requesting the URL) the phone can retrieve the URL from the cache instead of requesting it from the UP.Link server. This gives the user a perception of enhanced performance. There is no guarantee that the phone will be able to prefetch the specified URL. For example, if the phone is on a circuit-switched network and the circuit is down, the phone will not open a circuit. If the phone fails to execute the prefetch, it does not retry it.
If you specify the
If several tasks on a card specify the | |
If the DEST option specifies a URL, the method used to request the URL:
If you do not specify this option, the default,
It is strongly recommended that you use the | |
The data to post if the | |
Specifies the character set which the HDML application expects data returned from the phone to use. It can specify character set names, such as the following:
For a complete list of character set names, see Supporting multiple character sets
If you do not specify the | |
A list of variables to set for the current activity (if the task is
Variable values must be escaped according to URL escaping conventions. The phone unescapes the | |
A semicolon-delimited list of variables to which the phone stores the return values from a The phone stores return values according to ordinal position. For example, if you specify the following option:
the phone stores the first return value to
If you want to skip a return value, you must include a semicolon as a placeholder. For example, to ignore the first return value and store the second return value to | |
A semicolon-delimited list of values that an activity invoked with The values must be escaped according to URL escaping conventions. | |
The URL to request after a nested activity returns.
If the | |
The URL to request after a nested activity invoked by a
If the | |
A boolean value specifying whether the nested activity specified in a
To indicate the nested activity is friendly, specify | |
A boolean value specifying whether the UP.Browser should provide the URL of the current deck when requesting the URL specified by the The UP.Browser attempts to use the shortest possible relative URL in the "Referer" header if possible. | |
A boolean value specifying whether a
The phone ignores the | |
>
| |
The text for the link. The phone displays this text in square brackets ( | |
</A>
|
The following HDML defines the card shown in Figure 2-1.
FIGURE 2-1. Display card containing links