HTML Navigation

Kalipso - Form - Actions - Actions Description - Group Controls - HTML Navigation

Used to make the specified HTML control display an HTML from a URL address, a local file, or navigate back/forward in navigation history. Also allows to refresh the current content or stop the current content loading process.

Action available for the following operating systems:

Parameters

• HTML Control <unquoted string> - The HTML control to make the navigation.

• Navigation Type <numeric> - The type of navigation to perform. The possible values are:

  • 1. Address. This option allows navigation to a specified address.

    2. Back. This option navigates back in navigation history, like in typical web browsers.

    3. Forward. This option navigates forward in navigation history, like in typical web browsers.

    4. Stop. This option stops loading the current web page, like in typical web browsers.

    5. Refresh. This option reloads the current webpage, like in typical web browsers.

The next parameters are only valid when Navigation Type is "1-Address"

• Mode <numeric> - The HTTP request type to make. It can be either a "1-GET" or a "2-POST" request. Normally to show a webpage you would use "GET", but POST can be used to POST data to a webserver, like a form data.

• Address <string> - The address of the HTML content to load. It can be an web address, like "http://www.google.pt", but it can also be used to load local data, for example: "file://"+PFOLDER+"\MyPage.html" will load the "MyPage.html" from the project folder.

• Additional Header <string> - Additional HTTP headers to send in the request to the webserver.

• Encoding <numeric> - Encoding for the Post Data if Post Data is specified. Valid options are: 1-utf-8, 2-utf-7, 3-ansi, 4-unicode (UTF16), 5-bytes (raw bytes are sent, no encoding is performed).

• Post Data <string> - Post Data to send in the request to the webserver. This is only valid if the request mode is "2-POST".

Additional Headers on Win32 do not override default headers.

On Android additional headers key may be changed to lowercase, but this does not violate HTTP standard (see RFC 7230, section 3.2).