Task Elements

• <go> tag - The go element can contain one or more postfield elements. If the destination of a go element is a card within the same deck, all of the postfield elements will be ignored. The go element can also contain one or more setvar elements. Unlike postfield elements, there are no destination limitations on passing information contained in the setvar elements. The <go> nested tags (postfield and setvar) are supported.

  Attribute	Value	Description	Comments
  href	url	REQUIRED	SUPPORTED
  accept-charset	Charset_list	A comma- or space-separated list of character encoding the server must be able to process. The default value is "unknown".	SUPPORTED
  method	post get	Sets how to send the data to the server. Default method is get. When method=”get”, the data is sent as a request with?data appended to the URL. The disadvantage of get is that it can be used only for a limited amount of data; if you send sensitive information it will be displayed on the screen and saved in the web server's logs.With method=”post”, the data is sent as a request with the data sent in the body of the request. This method has no limit, and sensitive information is not visible.	SUPPORTED
  sendreferer	true false	If set to true, the browser sends the URL of the current deck with the request, which allow servers to perform simple access control on decks, based on which decks are linking to them. Default is “false”	SUPPORTED

• <noop> tag - The noop tag dictates that no operation should be done. This tag can be used on the card level to prevent an event, specified on the deck level by the template element, from occurring. It can only be contained in either a do or onevent element.

An example of noop is to use a <do> tag to add a "Back" link to the card. When users click on the "Back" link, generally they should be taken back to the previous card. However, the <noop> tag prevents this operation; when the user clicks on the "Back" link nothing happens.

• <prev> tag - The prev tag specifies navigation to the previous URL in the history.
• <refresh> tag - The refresh tag specifies a refresh task whereby the whatever card is being displayed will be refreshed. This task specifies the need for an update of the user agent context as specified by the contained <setvar> elements.This tag can only be nested inside an anchor, do, or onevent element. Xml:lang is not an associated attribute. User-visible side effects of the update can occur during the processing of the <refresh>.