BlackBerry Browser Version 3.2. Technical Reference Guide

Transcription

1 BlackBerry Browser Version 3.2 Technical Reference Guide

2 BlackBerry Browser Version 3.2 Technical Reference Guide Last revised: 12 March 2002 Part number: PDF At the time of printing, this documentation complies with the BlackBerry Wireless Handheld version Research In Motion Limited. All Rights Reserved. The BlackBerry and RIM families of related marks, images and symbols are the exclusive properties of Research In Motion Limited. RIM, Research In Motion, Always On, Always Connected, the envelope in motion symbol and the BlackBerry logo are registered with the U.S. Patent and Trademark Office and may be pending or registered in other countries. All other brands, product names, company names, trademarks and service marks are the properties of their respective owners. The handheld and/or associated software are protected by copyright, international treaties and various patents, including one or more of the following U.S. patents: 6,278,442; 6,271,605; 6,219,694; 6,075,470; 6,073,318; D445,428; D433,460; D416,256. Other patents are registered or pending in various countries around the world. Visit for a current listing of applicable patents. While every effort has been made to ensure technical accuracy, information in this document is subject to change without notice and does not represent a commitment on the part of Research In Motion Limited, or any of its subsidiaries, affiliates, agents, licensors, or resellers. There are no warranties, express or implied, with respect to the content of this document. Research In Motion Limited 295 Phillip Street Waterloo, ON N2L 3W8 Canada Produced in Canada

3 Contents About this guide... 5 Further reading...6 Browser versions...6 CHAPTER 1 Getting started... 7 Browser properties...8 Web access methods...9 Content...11 Networks...12 User experience...12 CHAPTER 2 Browser features History...13 Cookies...14 Cache...14 Bookmarks...14 Images...15 CHAPTER 3 Browser interface Browser screen...18 Menus...19 Links...20 Option lists...20 CHAPTER 4 Provisioning Service book entries...21 Browser profiles...22 User options...23

4 CHAPTER 5 Push applications Browser push system Push methods Writing a push application CHAPTER 6 Browser security Wireless TLS HTTP over SSL/TLS CHAPTER 7 WML support WML rendering WML design considerations CHAPTER 8 HTML support HTML rendering Examples of HTML pages HTML design considerations HTML filtering APPENDIX A WML reference APPENDIX B HTML reference Acronym list... 59

5 About this guide This document provides a technical overview of the BlackBerry Wireless Handheld Browser application to assist developers in creating usable, web-based applications as part of the BlackBerry solution. This document explains the following topics: Browser characteristics protocol implementations provisioning writing push applications secure browsing support WML implementation reference HTML implementation reference

6 About this guide Further reading The following additional documentation can help you use the BlackBerry Wireless Handheld and develop applications for it. Document Mobile Data Service Network Programmer Guide BlackBerry Java Development Environment Developer Guide BlackBerry Wireless Handheld User Guide Description explains how to write server-side push applications and transcoders for the BlackBerry Enterprise Server Mobile Data Service explains how to write Java applications for the handheld explains how to use the handheld, including the Browser application Browser versions Unless otherwise noted, the information contained in this white paper applies to the BlackBerry Wireless Handheld, Version 3.2 or later. The following features are supported only in version or later: HTML display (version 3.2 supports WML only) wireless TLS (WTLS) encryption 6 BlackBerry Browser

7 Chapter 1 Getting started The BlackBerry 5810 Wireless Handheld and BlackBerry 5820 Wireless Handheld include a fully featured, graphical Internet browser that integrates seamlessly into the BlackBerry user experience. The chapter summarizes the capabilities of the Browser application: Browser properties markup languages networks protocols user experience

8 Chapter 1: Getting started Browser properties The BlackBerry Browser application has been designed to function well even under adverse operating conditions, such as limited memory or power on the handheld, or unreliable bandwidth or connectivity on the wireless network. The following table summarizes browser properties: Property Operating system Screen size Screen color CPU speed Fonts Memory User input and navigation Lines of display Characters per line Links WML do labels Handheld Browser Java 2 Platform, Micro Edition (J2ME) 160 x 160 pixels monochrome 32.5 MHz variable-width system font supports all keyboard characters supports both uppercase and lowercase letters user can set to 8, 10 or 12-point type 8 MB standard keyboard and trackwheel 12 lines of text with 12-point type 14 lines of text with 10-point type 18 lines of text with 8-point type 35 characters per line with 8-point or 10-point type 28 characters per line with 12-point type displayed with a dotted underline links automatically launch appropriate application (Browser, Messages, Phone) associated with menu items 8 BlackBerry Browser

9 Web access methods Web access methods The BlackBerry Browser implements two complementary protocol stacks, which use different gateways to the Internet: Protocol Gateways Description WAP 1.1 HTTP/IPPP any WAP-compliant gateway, without proprietary extensions (must support WTP-level segmentation and reassembly) BlackBerry Enterprise Server with Mobile Data Service extensions supports WAP 1.1 features, including WML 1.3, WMLScript 1.2, and WTLS WAP push applications are not supported supports secure access to corporate intranets, including push applications and custom plug-ins for data parsing and conversion supports HTTP over SSL/TLS These two protocol stacks provide flexibility in how users access web content. Service providers and network operators can provision handhelds over the wireless network for WAP support. Corporate administrators can use the IT Policy Manager to provision handhelds to support HTTP over the IP Proxy Protocol (IPPP). Using WAP The WAP protocol provides web browsing capabilities using standard WAP gateways. The Browser application supports WAP 1.1 features, including WML 1.3 and WMLScript 1.2. WAP push applications are not supported. The Browser application, version or later, supports WTLS for secure web transactions using WAP. Refer to "Browser security" on page 35 for more information. Research In Motion has performed interoperability testing with WAP gateways from Nokia and Openwave Systems. Technical Reference Guide 9

10 Chapter 1: Getting started Using HTTP/IPPP The IP Proxy Protocol (IPPP) enables corporate customers to provide secure access to corporate intranets using the BlackBerry Enterprise Server with Mobile Data Service extensions. The BlackBerry Enterprise Server is installed at corporate locations. Organizations can write Java applications to push information out to mobile users, and can also write plug-in transcoder applications to perform data filtering and conversion to and from the handheld. The Browser application supports HTTP over SSL or TLS for secure web transactions using HTTP/IPPP. Refer to "Browser security" on page 35 for more information. Switching between configurations Service providers or network operators can enable users to switch between the WAP and IPPP browser configurations, depending on whether the users are browsing the Internet or accessing a corporate intranet. Users change the Browser configuration by setting Browser options. 10 BlackBerry Browser

11 Content Content The following table summarizes BlackBerry Browser support for text and graphics: Feature Support Markup languages WML 1.3 Compact HTML (chtml) Scripts WMLScript 1.2 Graphics WAP Bitmaps (WBMP) Level 0 - Monochrome Portable Network Graphics (PNG) Graphic Interchange Format (GIF) In version 3.2, the Browser supports WML content only. In version 3.2.1, the Browser also supports chtml. The Browser has been designed with separate modules for each content type, such as WML or HTML. This built-in extensibility means that the Browser can support emerging standards, such as xhtml Basic and XHTML MP, as they become more widely used. Users can choose whether to accept WML or HTML content, or both. The Browser sends this setting in the Accept header of the HTTP request. This option enables users to control how they receive web content, depending on the type of content and gateway behavior. For example, users might want to indicate support for HTML to prevent WAP gateways from performing unwanted conversion of HTML to WML. In other cases, users might not want to indicate support for HTML to ensure that web sites with both WML and HTML content send the WML version. In HTML only mode, if a requested URL returns WML content, the origin server or gateway returns an HTTP response of 406 ( Not Acceptable ). The Browser then adds the WML capability to the Accept header and requests the same URL again. Refer to chapters 9 and 10 for information on how the Browser implements WML and HTML elements and attributes. Technical Reference Guide 11

12 Chapter 1: Getting started Networks User experience The BlackBerry Browser is designed for use with IP-based, packet-based wireless networks. The Browser is currently available on the BlackBerry 5810 and BlackBerry 5820 Wireless Handhelds, which operate on GPRS networks. To reduce the impact of browsing on the network, the handheld ends the current user session (PDP context) when the user closes the Browser. Service providers or network operators can also provision a session timeout to end the user session after a specified period of inactivity. At the gateway, service providers or network operators can impose a limit on page size that the Browser can request. The BlackBerry Wireless Handheld was designed specifically for data services, with a richer user interface and larger screen area than other wireless devices. The Browser takes advantage of the handheld keyboard, trackwheel, and large screen to provide a superior user experience that closely emulates PC-based web browsing. Users do not need to remember soft keys; they can navigate using the trackwheel. WML do elements appear as menu items. The Browser is integrated with other handheld applications to provide a seamless user experience. The Browser recognizes web addresses, addresses, and phone numbers, so that users can click a link to compose an message or place a phone call. Conversely, users can click URLs in messages to launch the Browser. The Browser provides specialized features to accommodate the constraints of mobile devices and wireless networks for efficient mobile browsing: Images are loaded in the background, after the requested page has been displayed, to speed up page display. Image placeholders are displayed until images become available. Users can choose to display images or to display image placeholders only. When a Browser request cannot be completed because the handheld is outside an area of wireless network coverage, the user can save the pending request to the messages list. The Browser then resends the request when the handheld returns to a coverage area. Users can receive notification when the requested page is ready to view. Users can choose to make Browser requests in the background, while they continue to view the current page. The request is saved to the messages list for completion. Users can define bookmarks for offline use to view content even when they are not in an area of wireless network coverage. 12 BlackBerry Browser

13 Chapter 2 Browser features History The chapter explains the following Browser features: history cookies cache bookmarks images The Browser maintains a navigation history of up to 20 items. When the history reaches 20 items, the least recently accessed pages are removed first. When a user navigates to an HTML page, the URL of the page is added to the navigation history. If memory on the handheld becomes low, the Browser removes history items to free memory. Users can access the history list by clicking History on the Browser main menu. Users can then use the trackwheel to select an item in the history.

14 Chapter 2: Browser features Cookies Cache Bookmarks The Browser supports standard cookies, including expiry settings. The browser maintains cookies when the handheld is turned off. Users can clear stored cookies at any time. Network operators or service providers can enable or disable cookie support on the handheld and set the size of the cookie cache. Users cannot view or change these options. The Browser maintains a cache of viewed web pages, and loads requested content from the local cache whenever possible. Users can clear the page or raw data cache at any time. The Browser respects all cache control directives that origin servers send in responses, such as Expires, Max-Age, and Cache-Control. The Browser always retrieves content for a requested URL from the cache, when permitted, based on associated cache control directives. Because the Browser is integrated into the BlackBerry application environment, the Browser cache removes content when necessary to free memory. Expired pages are always removed first, followed by pages accessed least recently. Network operators or service providers can set the size of both the raw data and the page cache. The system default for both is 10. Users cannot view or change these options. The BlackBerry Browser provides robust bookmark support that combines the ease-of-use expected from PC-based browsers as well as added features that are especially useful in a wireless environment. Users can add bookmarks to any page that they visit, and can create a hierarchy of folders to organize the bookmarks. Users can edit the title and URL of bookmarks. Users can also search bookmarks, in the same way that they can search their Address Book. Frequently used Browser pages can be saved to the Messages list for quick access. Bookmarks can be especially useful in situations when users are outside an area of wireless network coverage. When users add a bookmark, they can choose to make the bookmark available offline, which means that the actual content of the page is saved as well as the URL. 14 BlackBerry Browser

15 Images Offline bookmarks for web pages that contain forms also save the current values of form fields, which users can use as a template for frequently used forms. For example, users can add an offline bookmark for a page that contains a form. Later, even if the user is outside an area of wireless network coverage, users can load the bookmarked form, fill out the appropriate fields, and submit it. Users can then save the Browser request to the Messages list. When the handheld returns to coverage, the Browser sends the request automatically. Users can back up browser bookmarks using the BlackBerry Desktop Manager, in the same way that they do with Address Book entries. This means that, for example, when users update their handheld with new software, their bookmarks can be retained. Images The Browser supports monochrome wireless bitmaps (WBMP Class 0), PNG, and GIF images. The Browser does not display other image types. The gateway must convert images into the appropriate type. For example, transcoders can be written for the BlackBerry Enterprise Server Mobile Data Service to convert images to PNG format. The Browser initially displays pages with placeholders for all images, with the alt text of the image, if provided. The Browser loads each image separately in the background and updates the page as images become available. The Browser retrieves images from the local cache if possible, in which case the image is displayed more quickly than an image that needs to be retrieved from the network. The Browser displays images in a separate vertical area from the content that is before and after the image. Images are not rendered inline with surrounding text. When images are located within an <a> or <anchor> element, users are able to select the image to follow the associated link or perform the associated action. Images outside an <a> or <anchor> element are not selectable. GIF support The browser processes GIF images for display on the handheld as follows: Images are scaled horizontally to be no more than 1.5 times the screen width. Images are not scaled vertically. Images are dithered into a monochrome image. After scaling, if the monochrome bitmap is more than 8192 bytes in size, the image is discarded. Technical Reference Guide 15

16 Chapter 2: Browser features 16 BlackBerry Browser

17 Chapter 3 Browser interface This chapter describes the BlackBerry Browser interface for both WML and HTML pages. This chapter explains the following topics: main screen menus links option lists

18 Chapter 3: Browser interface Browser screen The Browser displays a non-scrolling title section at the top of each page that displays the page title and also displays any status messages for requests. The title section is separated from the content section of the page by a horizontal line. Users roll the trackwheel to scroll up and down the page. Links to web pages, phone numbers, and address are underlined with a dotted line. When a link is selected, the user can activate the link by pressing Enter or by clicking the trackwheel to open the menu and then clicking Get Link. Figure 1: Main Browser screen 18 BlackBerry Browser

19 Menus Menus In the BlackBerry Browser, users do not use soft keys to access WML elements. Instead, users can use the trackwheel or keyboard to select menu items for WML elements. The Browser main menu provides access to most tasks that a user can perform when browsing. The menu provides the standard system menu items that are available for all BlackBerry applications, such as Hide Menu and Close. The Browser provides standard menu items for navigation, including Home, Next, Previous, History, and Refresh. A Go To menu item enables users to enter any URL. Figure 2: Browser menu Specific menu items appear depending on the page and which item is selected. For example, when a link is selected, users can choose the Get Link menu item to view that page. Technical Reference Guide 19

20 Chapter 3: Browser interface Links Links appear underlined with a dotted line. When the link is selected, users can follow the link either by selecting the Follow Link menu item or by pressing ENTER. On a web page, users can scroll to links by rolling the trackwheel. Scrolling up or down moves to the next or previous link on the same line, before moving to the next line. Option lists Figure 3: Browser hyperlinks Option lists are displayed as either radio buttons (for single-selection lists) or check boxes (for multiple-selection lists). Users can select an option in a list by pressing SPACE or by clicking the Select Option menu item. Figure 4: Browser option lists 20 BlackBerry Browser

21 Chapter 4 Provisioning The BlackBerry Browser provides many options to enable network and service providers, as well as users, to control the Browser effectively. This chapter explains the following topics: service book entries Browser profiles user options Service book entries Network operators and service providers and provision the handheld to support one or more services. These service entries define the protocol stack to use (WAP or HTTP/IPPP) as well as gateway connection information. The service entries also define a home page (URL) and several browser settings. They are listed on the Service Book options screen. The WAP service provides general web browsing through standard WAP gateways. The IPPP service provides secure access to corporate intranets and services through the BlackBerry Enterprise Server. The service provider or network operator provisions WAP services over the air during handheld registration. In version 3.2, IPPP services are also provisioned during registration if a corporate browser is provided. In version or later, system administrators provision IPPP services using the BlackBerry Enterprise Server. The Browser retrieves the appropriate services automatically from IT Policy. Service entries occur in pairs: one entry defines the Browser configuration and the other entry defines the transport configuration.

22 Chapter 4: Provisioning Browser profiles Network operators and service providers can provision one or more Browser profiles, including a default profile. This provisioning is performed over the air during handheld registration. Two browser profiles are typically provided: WAP browser corporate browser The Browser profile defines the following options. Option Choose Browser Config Home page address On startup, load Session Timeout Config Values Editable Secure Access Description Users can switch between two or more Browser profiles. Some corporate users, for example, might use WAP service for general browsing and IPPP services for accessing the corporate intranet. If they have the appropriate permission, users can change the home page address. Users can return to the home page at any time by clicking the Home menu item. Users can choose which page to display when the Browser starts: bookmarks, home page, or last page loaded. Network operators or service providers can set a session timeout to end the user s session after a specific period of inactivity. The network operator or service provider can choose whether or not to allow users to modify these settings. When a WAP Browser configuration is selected, network operators or service providers can configure whether or not to enable secure WAP connections using WTLS. 22 BlackBerry Browser

23 User options User options Users can set the following options. Option Content Mode Emulation Mode Load Images Show Image Placeholders Confirm Delete Bookmarks Confirm Execute WML Scripts Start Links on New Line Description Users can choose which type of content to accept: WML and HTML, HTML only, WML only. The browser includes this setting in the HTTP Accept header. Users might want to indicate support for HTML to prevent WAP gateways from converting HTML to WML. In other cases, users might not want to indicate support for HTML, to ensure that web sites with both WML and HMTL send the WML content. Users can choose to advertise the Browser type as one of the following: RIM, Microsoft IE, MS Pocket IE, Netscape. This value is sent to servers in the User-Agent header field. Certain web sites send different content based on this field. RIM emulation sets the User-Agent field to BlackBerry/3.2 or BlackBerry/3.2.1, depending on the Browser release. Users can disable this option to prevent the loading of images. Users can disable this option so that placeholders are not shown when images are not available. Users can choose whether or not they receive a confirmation dialog box when they delete bookmarks. Users can choose whether or not they are prompted before WML scripts are executed. Users can choose to have hyperlinks appear on separate lines. Technical Reference Guide 23

24 Chapter 4: Provisioning 24 BlackBerry Browser

25 Chapter 5 Push applications The BlackBerry browser supports push applications through the BlackBerry Enterprise Server Mobile Data Service. The Browser does not support WAP push applications. This chapter explains the following topics: Browser push system on the handheld methods of pushing data to the handheld how to write a Browser push application Browser push system The BlackBerry Enterprise Server, with Mobile Data Service extensions, is required to push data to the handheld. The handheld must also be provisioned with the IPPP Transport and IPPP Browser Config service book entries. Refer to "Service book entries" on page 21 for more information. Applications push content to the handheld using HTTP POST requests to the BlackBerry Enterprise Server. On the handheld, a separate push listener thread listens on port 7874 for incoming messages and processes those messages. If a service book entry is added or changed, the push threads are modified accordingly. Each pushed message can include the content and several attributes. Attributes are encoded as HTTP headers, as listed in the following table.

26 Chapter 5: Push applications Attribute HTTP Header Values Type X-Rim-Push-Type Browser-Message Browser-Channel Browser-Content Channel ID X-Rim-Push-Channel-ID <unique string> Title X-Rim-Push-Title <title> Read Icon URL X-Rim-Push-Read-Icon-URL <icon URL> Unread Icon URL X-Rim-Push-Unread-Icon-URL <icon URL> Ribbon Position X-Rim-Push-Ribbon-Position <position number> Description X-Rim-Push-Description <description string> Content Location Content-Location <content URL> Content Type Cache Cache Content-Type Cache-Control Expires Push methods Custom Java applications can be written for the BlackBerry Enterprise Server Mobile Data Service to push data to the handheld browser. Web content can be pushed to the Browser in one of the three ways: message list channel cache Message push Applications can push pages to the handheld which then appear as a Browser message in the handheld Messages list, along with messages. The pushed object can either include the content for display, or include only the URL for the Browser to fetch when the user requests it. The user can open the Browser message to open the browser at the specified page. 26 BlackBerry Browser

27 Push methods The message push request can include a title attribute, which then appears in the Messages list. Otherwise, the Browser message displays the URL. The application can include the content in the Browser message, so that the Browser renders the pushed content immediately. Alternatively, the application can include only the URL, so that the Browser performs a normal fetch operation to retrieve the content, from either the local cache or from the network. This type of push object requires the following attributes: URL, Title (optional), and Content (optional). A message push object can include the following attributes: URL title (optional) content (optional) Channel push Applications can push data to the handheld that create or update channels, which appear on the handheld Home screen with a custom icon. This effectively creates a Browser-based application on the handheld for regular updates of certain types of pushed data. A channel push request can include URLs to the location of two icons to display on the Home screen: one icon to display when content is new (unread) and another icon to indicate that the content has been read. Icons must be.png files to be displayed on the handheld. Monochrome, 28 x 28 pixel.png images are recommended. The message can also specify which position on the Home screen the channel should occupy. A channel push object can include the following attributes: channel ID content URL title (optional) read icon URL (optional) unread icon URL (optional) description (optional) Home screen position (optional) content (optional) When the handheld receives a channel push message, it creates a new channel, or updates the channel if it already exists. The specified Unread Icon is displayed on the Home screen to indicate to users that the content has been updated. By replacing Technical Reference Guide 27

28 Chapter 5: Push applications existing channels, a push application can change the Home screen icon in real time. For example, a weather forecast channel could dynamically change the weather icon as forecasted conditions change. On the Home screen, the user can click the channel icon to display the pushed content in the Browser. The icon then changes to the specified Read icon. Cache push Applications can push content directly to the Browser s persistent cache. There is no indication to the user that the content has been updated. The next time that the user visits the specified URL, the Browser retrieves the content from the cache. Pushing data to the cache enables users to access the content quickly, even when they are outside an area of wireless network coverage. A cache push object can include the following attributes: content URL content A cache push message can also include cache control and expiry fields. 28 BlackBerry Browser

29 Writing a push application Writing a push application The following example demonstrates how to write a Java application that pushes data to the handheld Browser. This is an example of writing a channel push application. Refer to "Channel push" on page 27 for more information. A push application must make two requests: an HTTP GET request to retrieve content from the content server an HTTP POST request to send content to the BlackBerry Enterprise Server The format of the HTTP POST request is as follows: The BlackBerry Enterprise Server, using the Mobile Data Service, routes the push request to the specified handhelds. For more information on writing push applications, refer to the Mobile Data Service Programmer Guide. Writing a push method As part of writing a push application, you must define a method to retrieve content and push it to a handheld user through the BlackBerry Enterprise Server. 1. Define a method that accepts as parameters all the required attributes for a channel push. Refer to "Browser push system" on page 25 for more information. public static void pushpage(string beshostname, int besport, String pin,string pushurlstring, String pushtype, String pushtitle, String unreadiconurl, String readiconurl) { 2. Define variables for connections to two URLs: one to the server with the content and one to the BlackBerry Enterprise Server.... HttpURLConnection pushconn; HttpURLConnection besconn; URL pushurl; URL besurl; 3. Create the connection to the BlackBerry Enterprise Server by invoking the openconnection method on the URL. The push listener thread on the handheld listens on port besurl = new URL("http", beshostname, besport, "push?destination=" + pin + "&PORT=7874&REQUESTURI=/"); besconn = (HttpURLConnection)besUrl.openConnection(); 4. Create the connection to the content server by invoking the openconnection method on the URL. pushurl = new URL(pushUrlString); pushconn = (HttpURLConnection)pushUrl.openConnection(); Technical Reference Guide 29

30 Chapter 5: Push applications 5. Set properties for the HTTP GET request to the content server. pushconn.setallowuserinteraction(false); pushconn.setdoinput(true); pushconn.setdooutput(false); pushconn.setrequestmethod("get"); 6. Open the connection to the content server. pushconn.connect(); 7. Set properties for the HTTP POST request to the BlackBerry Enterprise Server. First, copy header properties from the GET request and then set additional properties for the push. String name, value; for (int i = 0; true; i++) { name = pushconn.getheaderfieldkey(i); value = pushconn.getheaderfield(i); if ((name ==null) && (value == null)) { break; } if ((name ==null) (value == null)) { continue; } System.out.println("setting header property " + name + " = " + value); besconn.setrequestproperty(name, value); } besconn.setrequestproperty("content-location", pushurlstring); besconn.setrequestproperty("x-rim-push-title", pushtitle); besconn.setrequestproperty("x-rim-push-type", pushtype); besconn.setrequestproperty("x-rim-push-channel-id", pushurlstring); besconn.setrequestproperty("x-rim-push-unread-icon-url",unreadiconurl); besconn.setrequestproperty("x-rim-push-read-icon-url", readiconurl); besconn.setrequestmethod("post"); besconn.setallowuserinteraction(false); besconn.setdoinput(true); besconn.setdooutput(true); 8. Read content from the content server connection and write it to the BlackBerry Enterprise Server connection. InputStream ins = pushconn.getinputstream(); OutputStream outs = besconn.getoutputstream(); copystreams(ins, outs); Note: This step is optional for applications that use the channel or message push methods. If you do not push content to the handheld, the browser fetches the content when the user requests it. Note: This is a simple example for pushing content to one handheld. If you are pushing content to many users, you should first copy the content to a temporary file to avoid multiple requests to the content server. 9. Open the connection to the BlackBerry Enterprise Server. besconn.connect(); 30 BlackBerry Browser

31 Writing a push application The following example demonstrates a push application that reads properties from a file. Example: BrowserChannelPush.java /* * BrowserChannelPush.java * * Copyright 2002 Research in Motion Limited. All rights reserved. */ package com.rim.test.browserchannelpush; import java.net.*; import java.io.*; import java.util.*; public class BrowserChannelPush { private static final String CHANNEL = "Browser-Channel"; // private static final String MESSAGE = "Browser-Message"; // private static final String CONTENT = "Browser-Content"; private static final String PROPERTIES_FILE = "com/rim/test/browserchannelpush/push.properties"; public BrowserChannelPush() { } /** * Main method to reads the property file and perform the push. */ public static void main(string[] args) { // load the properties file Properties prop = new Properties(); try { prop.load(new FileInputStream(PROPERTIES_FILE)); } catch (FileNotFoundException fnfe) { throw new RuntimeException("property file not found: " + fnfe.getmessage()); } catch (IOException ioe) { throw new RuntimeException("problems reading property file: " + ioe.getmessage()); } // Hostname and Port of the BlackBerry Enterprise Server (BES) to // perform the push String beshostname = prop.getproperty("beshostname"); int besport = (new Integer(prop.getProperty("besPort"))).intValue(); Technical Reference Guide 31

32 Chapter 5: Push applications // The handheld PIN to which to push the page String pin = prop.getproperty("pin"); // The URL of the page to push String pushurlstring = prop.getproperty("pushurlstring"); String pushtype = prop.getproperty("pushtype").trim(); String pushtitle = prop.getproperty("pushtitle"); // URLs of the icons to use for Browser-Channel push type String unreadiconurl = prop.getproperty("unreadiconurl"); String readiconurl = prop.getproperty("readiconurl"); // push the page to the device pushpage(beshostname, besport, pin, pushurlstring, pushtype, pushtitle, unreadiconurl, readiconurl); } /** * Pushes a web page to a device. */ public static void pushpage(string beshostname, int besport, String pin, String pushurlstring, String pushtype, String pushtitle, String unreadiconurl, String readiconurl) { System.out.println("besHostName = " + beshostname); System.out.println("besPort = " + besport); System.out.println("pin = " + pin); System.out.println("pushUrlString = " + pushurlstring); System.out.println("pushType = " + pushtype); System.out.println("pushTitle = " + pushtitle); System.out.println("unreadIconUrl = " + unreadiconurl); System.out.println("readIconUrl = " + readiconurl); /* Two HttpURLConnections are used. One connects to the URL of the * page to push and reads the page from there. The other * connects to the BES and writes the page to it to push it to the * device */ HttpURLConnection pushconn, besconn; URL pushurl, besurl; try { besurl = new URL("http", beshostname, besport, "push?destination=" + pin + "&PORT=7874&REQUESTURI=/"); besconn = (HttpURLConnection)besUrl.openConnection(); try { pushurl = new URL(pushUrlString); } catch (MalformedURLException e) { 32 BlackBerry Browser

33 Writing a push application throw new RuntimeException("invalid push URL: " + e.getmessage()); } pushconn = (HttpURLConnection)pushUrl.openConnection(); pushconn.setallowuserinteraction(false); pushconn.setdoinput(true); pushconn.setdooutput(false); pushconn.setrequestmethod("get"); pushconn.connect(); /* Read the header properties from the push connection and write them * to the BlackBerry Enterprise Server connection. */ String name, value; for (int i = 0; true; i++) { name = pushconn.getheaderfieldkey(i); value = pushconn.getheaderfield(i); if ((name ==null) && (value == null)) { break; } if ((name ==null) (value == null)) { continue; } System.out.println("setting header property " + name + " = " + value); besconn.setrequestproperty(name, value); } /* Set additional header properties for the push. */ besconn.setrequestproperty("content-location", pushurlstring); besconn.setrequestproperty("x-rim-push-title", pushtitle); besconn.setrequestproperty("x-rim-push-type", pushtype); besconn.setrequestproperty("x-rim-push-channel-id", pushurlstring); besconn.setrequestproperty("x-rim-push-unread-icon-url", unreadiconurl); besconn.setrequestproperty("x-rim-push-read-icon-url", readiconurl); try { besconn.setrequestmethod("post"); } catch (ProtocolException e) { throw new RuntimeException("problems setting request method: " + e.getmessage()); } besconn.setallowuserinteraction(false); besconn.setdoinput(true); besconn.setdooutput(true); /* Read content from the push connection and write it to the * BlackBerry Enterprise Server connection. */ InputStream ins = pushconn.getinputstream(); OutputStream outs = besconn.getoutputstream(); Technical Reference Guide 33

34 Chapter 5: Push applications copystreams(ins, outs); besconn.connect(); if (besconn.getresponsecode()!= HttpURLConnection.HTTP_OK) { throw new RuntimeException("Couldn't push data to ippp, message: " + besconn.getresponsemessage()); } } catch (IOException e) { throw new RuntimeException("Couldn't push data to ippp, message: " + e.getmessage()); } } /** * Reads data from the input stream and copies it to the output stream */ private static void copystreams(inputstream ins, OutputStream outs) throws IOException { int maxread = 1024; byte [] buffer = new byte[1024]; int bytesread; for(;;) { bytesread = ins.read(buffer); if (bytesread <= 0) {break;} outs.write(buffer, 0, bytesread); } } } 34 BlackBerry Browser

35 Chapter 6 Browser security This section describes the supported security features for both the WAP and HTTP/IPPP protocols. Two security protocols are supported: Wireless TLS (WTLS) HTTP over SSL/TLS (HTTPS) HTTPS is supported in version 3.2 or later of the Browser. WTLS is supported in version or later of the Browser. WTLS can be used with the WAP stack using a WAP gateway. HTTPS can only be used with the HTTP/IPPP stack using the BlackBerry Enterprise Server Mobile Data Service. Note: With the HTTP/IPPP stack, data exchanged between the handheld and the BlackBerry Enterprise Server at the corporate location is always encrypted using the same Triple DES encryption that is used for . SSL/TLS provides an additional level of data security.

36 Chapter 6: Browser security Wireless TLS The BlackBerry Browser, version or later, supports WTLS Class 3, including both server and client certificates. Network operators and service providers can provision handhelds over the air to enable or disable WTLS support. The Browser supports both DES and RC5 encryption (40, 56, 64, 128 and 168-bit). The Browser does not support the WMLScriptCrypto library in this release. Figure 4 shows communication with WTLS security. Figure 5: WTLS Security Communication over the wireless network between the handheld and the WAP gateway is encrypted in WTLS. Communication over the Internet between the WAP gateway and the origin server is encrypted in SSL or TLS. The WAP gateway decrypts data it receives from either the handheld or the origin server and re-encrypts it using the appropriate protocol. In the WAP gateway, at the network operator or service provider location, data is not encrypted. 36 BlackBerry Browser

37 HTTP over SSL/TLS HTTP over SSL/TLS The BlackBerry Enterprise Server performs SSL handshaking and sets up the SSL connection on behalf of the handheld. Communication over the wireless network between the handheld and BlackBerry Enterprise Server is not encrypted using SSL; it is encrypted with the same Triple DES encryption that is used for . Communication over the Internet between the BlackBerry Enterprise Server and the origin server is encrypted over SSL or TLS. Corporate administrators manage trusted certificates and other security policies at the BlackBerry Enterprise Server. Figure 5 shows SSL/TLS communication in proxy mode. Figure 6: SSL/TLS Security: Proxy Mode In this proxy mode, there is a point at the BlackBerry Enterprise Server when data is not encrypted. In contrast to WTLS, however, data remains protected behind the corporate firewall. Technical Reference Guide 37

38 Chapter 6: Browser security 38 BlackBerry Browser

39 Chapter 7 WML support WML rendering This chapter describes how the BlackBerry Browser displays WML content and provides guidelines for creating WML content. The BlackBerry Wireless Handheld has a much richer user interface and larger screen area than other wireless devices, such as phones. User input Unlike many other WAP browsers, the BlackBerry Browser renders WAP input and select elements in full on every card that is displayed. User can scroll up and down to navigate to any of the elements on the displayed page. Actions Figure 7: Example of a form All do elements defined on a given card are accessible through menus, rather than soft keys. The label attribute of the do element is displayed as the menu item, if it is included; otherwise, a default label for the type of do element is displayed, such as Accept, Prev, Help, Reset, Options, Delete.

40 Chapter 7: WML support Option lists Figure 8: Example of do elements as menu items WML select items are displayed either as a list of radio buttons (for single selection) or as a list of check boxes (for multiple selection). Users can use the trackwheel or keyboard to navigate through the options, and click the Select Option menu item or press SPACE to select an option. Figure 9: Example of a select list 40 BlackBerry Browser

41 WML design considerations WML design considerations The main difference between the handheld Browser and the Browser on other devices is that do items appear on the Browser menu, whereas on other devices, do items are typically accessible using soft keys. Users must click the trackwheel to open the menu to see the do items on a page. If you are writing WML pages for the BlackBerry Wireless Handheld, you can use links on the page instead of do items. The larger screen size of the handheld makes it possible to use links. As a long as pages are kept fairly short, users can navigate easily through a page using the keyboard keys or the trackwheel. If you use do items, you should include reminders on the page to indicate that users should open the Browser menu to access these items. Testing When you design content for the BlackBerry Browser, you should test content in the Browser throughout the design and creation process to verify that the page works well on the handheld. You can test content using an actual handheld or using the BlackBerry simulator. The simulator is included with the BlackBerry Java Development Environment. Technical Reference Guide 41

42 Chapter 7: WML support 42 BlackBerry Browser

43 Chapter 8 HTML support HTML rendering The BlackBerry Browser, version or later, displays HTML content. This chapter describes how the BlackBerry Browser, renders HTML and provides guidelines for creating HTML content. Refer to Appendix B for a complete list of supported HTML elements and attributes. The BlackBerry Browser supports compact HTML (chtml), as defined in the W3C Note. chtml pages are typically 10 KB or less. The Browser ignores any tags that are not part of chtml and renders content as if the tags were not present. Compact HTML is a subset of HTML that excludes the following features: JPEG images tables image maps multiple character fonts and styles background colors and images frames style sheets The BlackBerry Browser does not support the direction selection of anchors using number buttons (which is part of the chtml recommendation). The BlackBerry Browser implements the following buffer limits, as recommended in the W3C Note: 512 bytes for INPUT and 4096 bytes for SELECT.

44 Chapter 8: HTML support Examples of HTML pages The following examples illustrate how the BlackBerry Browser displays various types of HTML content. Figure 10: Example of an HTML page Figure 11: Example of an HTML form 44 BlackBerry Browser

45 HTML design considerations HTML design considerations Figure 12: Example of image display When possible, write HTML pages using only the support chtml elements to improve the display of content in the Browser. Avoid using unsupported elements, such as tables or frames, for page layout. Do not use fonts or color to convey important information, because this information is not conveyed in the Browser. Images Use monochrome images, or test color images on the handheld Browser to verify that they are meaningful in a monochrome display. Use images that are less than 160 by 160 pixels in display size so that they display on the screen without requiring the user to scroll. Keep the image file size as small as possible. Testing When you design content for the BlackBerry Browser, you should test content in the browser throughout the design and creation process to verify that the page works well on the handheld. You can test content using an actual handheld or using the BlackBerry simulator. The simulator is included with the BlackBerry Java Development Environment. Technical Reference Guide 45

46 Chapter 8: HTML support HTML filtering The Browser can display HTML content through either a standard WAP gateway or the BlackBerry Enterprise Server. The Browser does not render all HTML tags completely. The Browser ignores any tags that are not part of chtml and displays the enclosed content as if the tags were not present. The optimal solution is to perform server-side filtering to convert HTML content to chtml before sending the page over the wireless network to the handheld. This server-side filtering can improve content display on the handheld, decrease rendering time, and minimize network latency. Figure 13: HTML rendering The BlackBerry Enterprise Server Mobile Data Service provides built-in support for transcoders. Corporate customers can write plug-in Java applications to perform customized content filtering and conversion. Refer to the Mobile Data Service Network Programmer Guide for more information. 46 BlackBerry Browser

47 Appendix A WML reference The following table summarizes Browser support for each WML element and attribute, in alphabetical order. Element Attribute Description #PCDATA All text is rendered in the font that corresponds to the current emphasis context in which the text occurs. a The a element specifies a link to be followed. href title accesskey The Browser goes to the link specified by the href attribute, first substituting any variable references from the WAP Context. Ignored. Ignored. access If specified, the Browser compares the access element to the domain and path specified in the access element to determine if the caller has the proper access to display the page. If not, the Browser displays an error message to the user. domain path The Browser uses the domain to verify access privileges. The Browser uses the path to verify access privileges. anchor When the user moves the cursor over a character or image that is contained in the anchor element, the user can choose the Follow Link menu item to perform the go, prev, or refresh task associated with the anchor element. title accesskey Ignored. Ignored. b Text in the b element is rendered in bold in the current font and size, if available. Otherwise, the standard font is used. Technical Reference Guide 47

48 Chapter 9: WML reference Element Attribute Description big Text in the big element is displayed in the next larger size of the current font, if available. Nesting of big and small elements is respected. br A new line is started where a br element occurs. card The card element contains the entire card. title newcontext ordered onenterforward oneenterbackward ontimer Displays the card title in the Title area of the screen If set to true, this attribute clears the variable in store. Ignored. All elements in a page are rendered. If specified, the specified URL is executed on enterforward events If specified, the specified URL is executed on enterbackward events If specified, the specified URL is executed on card timeout values. do The do element appears as a menu item. If a label attribute is not included, a default name is assigned to the menu item based on type. type label name optional The do element of type accept appears first on the menu. The type attribute is also used to match with do elements in the deck template, when the name attibute is not defined, for shadowing purposes. The label attribute is used as the label for the associated menu item. The name attribute is used to match with do elements in the deck template for shadowing purposes. do elements with the optional attribute set appear after other do elements in the menu. em Text in the em element appears in italic in the current font, if available. Otherwise, the standard font is used. fieldset Ignored. Enclosed elements are rendered as if the fieldset element did not exist. 48 BlackBerry Browser

49 Element Attribute Description go When an event specifies that a go task must be performed, the Browser goes to the specified URI. In addition, the Browser sets any variables specified in setvar elements within the go, and includes any values specified in contained postfield elements. href sendreferer method enctype cache-control accept-charset The Browser goes to the URI specified in this attribute. If yes, the referring URI is sent in the request. Both GET and POST methods of sending requests are supported. Ignored. The default is used: application/x-www-form-urlencoded. If this attribute is set to "no-cache", a flag is set on the request being sent to invalidate this page in the cache, if it is there, before retrieving (thus forcing retrieval from the network). Ignored. UTF-8 is used. head Ignored. Also refer to the sections on access and meta elements. i Text in the i element is rendered in italics in the current font and size, if available. Otherwise, the standard font and size is used. img Images are not rendered inline with surrounding text. Images are rendered in a separate vertical area from the content that occurs before and after the image. When images that are contained in anchor or a elements, users can select the image. alt src localsrc The Browser displays the text specified by this attribute in the placeholder location. When the real image data arrives, the alt-text placeholder is replaced by the real image. Specifies the actual location of the image. No localsrc images are currently supported. Technical Reference Guide 49

50 Chapter 9: WML reference Element Attribute Description vspace hspace align height width Specifies the amount of white space to insert above and below the image. Specifies the amount of white space to insert to the left and right of the image. Ignored. The Browser does not support inline images. The height attribute specifies image height. The width attribute specifies image width. input An input element appears as a text field into which users can type text. If the user enters a value that is not consistent with the restrictions specified by the attributes in the given input element, the Browser displays a warning dialog box when the user tries to save the value, and does not allow the user to save it. Input boxes are rendered on a line by themselves, not inline with surrounding text. name type value format emptyok size maxlength tabindex title accesskey Name of the variable to set with any entered value. If type is set to password, the Browser displays an asterisk (*) for every character that is entered. The initial value that is displayed when the card is first rendered. This value is used only when the variable specified by the name attribute is not already set in the WAP Context. If the variable is set, the current value of that variable is be used instead. If specified, the input field ensures that any entered text conforms to the mask specified by this attribute. If the emptyok attribute is set to "true", the Browser does not allow the user to enter any data into the input field. The size attribute specifies the size, in characters, of the input box. The maxlength attribute specifies the maximum length of the entered text Ignored. Tabbing is not supported in this version of the Browser. Ignored. Ignored. 50 BlackBerry Browser

51 Element Attribute Description meta The meta element specifies generic name-value pairs relating to the deck. name http-equiv forua content scheme The meta element is ignored if the name attribute is specified. If specified, the browser examines the meta element to determine whether it is relevant and process it accordingly. This attribute is ignored if it is set to false. The content attribute is used as the HTTP header value. Ignored. noop The Browser effectively removes any do or onevent elements that contain noop elements from the current card. onevent All events defined by onevent elements are handled according to the specifications. type The type attribute identifies the event that needs to be handled; it is also used to match do elements in the deck template for shadowing. optgroup Ignored. Options in a select element are rendered as a flat list on the screen. option Specifies an item in a select list. All option elements are rendered in the manner specified by the enclosing select list. Users can scroll through lists and select or clear options either by clicking the Select Option or Deselect Option menu item or by pressing ENTER. value title onpick The value attribute specifies the value of the enclosing select variable, if the select element has a name attribute. Ignored. The Browser loads the specified URI if the option is selected. p When a new p element is encountered, the Browser starts a new line and renders content according to the attributes. For layout purposes, the p and br elements are the same. align mode The align attribute specifies the position of the contents of the p element on screen. Ignored. Content is always wrapped. Technical Reference Guide 51

52 Chapter 9: WML reference Element Attribute Description postfield The postfield name/value pairs contained in a go element are included in the HTTP request. All variable references in the name and value attributes of each postfield element are replaced with appropriate values from the WAP context. pre The content of the pre element is displayed using a fixed-space font. prev The inclusion of the prev element in do elements affects how menus are constructed. The Browser menu always contains at least one item that allows users to go back in the navigation history. If the current card does not contain any do elements with a prev task, the browser creates a separate Back menu item. If the current card contains one or more do elements that contain prev elements, the Browser does not create a separate menu item and, instead, relies on the do elements for that card to provide this behavior. refresh If an event occurs that has a refresh task, the browser first sets any variables that are specified in setvar elements that are contained in the refresh element. It then refreshes the current page using the updated WAP context. select The select element is used to present a select list to the user, and to enable the user to select one or more of the options. Select lists are fully displayed on every card. Users can scroll up and down between them. Single-selection lists are rendered as radio buttons. Multiple-selection lists are rendered as check boxes. Refer to the option element for more information. title name value iname ivalue multiple tabindex Ignored. Used as the variable name to set. If the variable named by the name attribute does not already contain a value, the value attribute, if specified, is used to determine the list of pre-selected options. The variable to be set with the (1-based) index of the selected option, as per the specs. The index(es) of the pre-selected option(s), used only if the variable specified by iname does not already have a value. If true, it is a multiple-selection list and is rendered as a list of check boxes. Ignored. Tabbing is not supported. 52 BlackBerry Browser

53 Element Attribute Description setvar Specifies a new value for a given variable in the WAP context. When a go, prev or refresh task is executed, the Browser first looks for any associated setvar elements and then updates the WAP context accordingly before executing the task. small Text in the small element is displayed in the next smaller size of the current font, if available. Nesting of big and small elements is respected. strong Text in the strong element is rendered in bold font of the current size, if available; otherwise, the standard font is used. table Supported. When the table is larger than the screen width, users can scroll horizontally across the table rows by holding SHIFT and rolling the trackwheel. Users can also collapse large tables so that all cells of the first row are arranged vertically instead of horizontally. title align columns tr td Ignored. The text in table columns is aligned according to the align value. The columns attribute specifies the number of columns in the table. Each tr element is a separate row. Each td element is a separate cell. The content of each td element is rendered within the boundary of each cell. template The template element is used to specify deck-level do or onevent items. These items are included in every card for the deck, unless the card has a more specific do or onevent that shadows those in the template. Attributes on template are handled as if they were actual oneevent definitions for the corresponding events. onenterforward onenterbackward ontimer This item is treated as an onenterforward onevent element with a go action. This item is treated as an onenterbackward onevent element with a go action. This item is treated as an ontimer onevent element with a go action. Technical Reference Guide 53

54 Chapter 9: WML reference Element Attribute Description timer The timer element specifies a timer for the current card. The Browser implements card timers according to the WML specifications. In particular, a refresh operation stops the timer, sets its corresponding variable to the current timer value, performs the refresh, and then resets the timer and resumes it. When the timer expires, the variable that is named by the name attribute is set to "0" before any ontimer tasks are executed. name value The name attribute specifies the variable name to be set with the timer value on card entry, exit and timer-expire events. The initial value that the timer should be set to on card-entry events. u Content in the u element is underlined in the current font and size, if available; otherwise, the standard font and size are used. 54 BlackBerry Browser

55 Appendix B HTML reference The following table summarizes Browser support for each HTML element and attribute, in alphabetical order. Element Attribute Description!- Ignored.!DOCTYPE Checked to ensure that the doctype declaration corresponds to an HTML doctype. &xxx; Character entities defined in the W3C Note on chtml are supported: &,, >, <, ",,, &#0;, and &#127;. A Contents are underlined with a dotted line. The following link schemes are supported: mailto:, tel: HREF NAME ACCESSKEY Activating the link opens the Browser, Message, or Phone application to the specified address. The Browser remembers the location as a target for other links. Ignored. BASE HREF The BASE element sets the base URL of the page. BLOCKQUOTE Contents are rendered with an indentation of one full-width space. BODY Ignored. No BODY attributes are supported. Non-white text is displayed as black. BR CLEAR A line break is inserted. The clear attribute is ignored. CENTER Content is centered on the screen. DD Text is rendered as a normal paragraph following the DT element, with the left margin shifted over by one space to the right. DIR Ignored. Enclosed LI elements are rendered as described below. Technical Reference Guide 55

56 Chapter 10: HTML reference Element Attribute Description DIV ALIGN Content is aligned according to the ALIGN attribute. DL Ignored. Enclosed DT and DD elements are rendered as described. DT Text is rendered as a normal paragraph. FORM Users can submit a form using the Submit INPUT element. On submission, the form collects the names and values of enclosed SELECT, INPUT, and TEXTAREA elements and submit the query as part of the request (GET) or as the post data (POST). ACTION METHOD ENCTYPE Provides the URI to which the form is submitted. The form query is submitted as part of the GET or POST request. Ignored. Form data is encoded with the content-type application/x-www-form-urlencoded. H1 to H6 Text in heading elements is rendered in bold. ALIGN Text is positioned on the screen according to the align value. HEAD Ignored. Used for grouping purposes only. HR ALIGN SIZE WIDTH NOSHADE The horizontal line is rendered according to the ALIGN, SIZE, and WIDTH attributes. Ignored. The Browser does not support 3D effects, such as shadowing. HTML VERSION Ignored. Used for grouping only. IMG The Browser supports.png and.gif graphics only. ALT SRC ALIGN WIDTH HEIGHT HSPACE VSPACE ALT BORDER The image is displayed according to specified attributes. ALT text is displayed when an image is unavailable; otherwise, a placeholder is displayed. 56 BlackBerry Browser

57 Element Attribute Description INPUT TYPE The Browser renders INPUT elements according to the value of the TYPE attribute: TYPE=FILE is not supported. TYPE=CHECKBOX The element is rendered using a checkbox control. Checkboxes can occur anywhere in a FORM element. Text and graphics cannot appear on the same line, so checkboxes appear on their own line before accompanying text. TYPE=HIDDEN Hidden elements are not displayed, but are included when the form is submitted. TYPE=PASSWORD Text that the user enters is displayed using asterisks. The actual value is included in encoded form data when the form is submitted. TYPE=RADIO The element is rendered using a radio control. Radio input elements can appear anywhere in a FORM element. Radio controls are displayed on their own line (text and images cannot appear on the same line). TYPE=RESET The element is rendered as a button. Users can use the trackwheel to scroll to the button and click it to reset the enclosing form to the original values. This does not affect other forms on the screen. TYPE=SUBMIT The element is rendered as a submit button. Users can use the trackwheel to scroll to the button and click it. TYPE=TEXT The element is rendered as a text input field. TYPE=IMG The associated image is rendered and made selectable. ACCESSKEY MAXSIZE SIZE Ignored. INPUT elements with TYPE set to PASSWORD or TEXT span the screen width, up to the value of MAXSIZE. Ignored. INPUT elements with TYPE set to PASSWORD or TEXT span the screen width, up to the value of MAXSIZE. LI LI elements are endered with a bullet character or number, depending on enclosing element (DIV, UL, or OL) MENU Same as UL. OL LI elements within OL appear with sequential numbers. First LI element is rendered on a new line. Refer to LI description for more information. OPTION SELECTED Encloses the text of an option in a SELECT list. Refer to SELECT for more information. Technical Reference Guide 57

58 Chapter 10: HTML reference Element Attribute Description P ALIGN Each P element starts on a new line, positioned on the screen according to the ALIGN attribute. PLAINTEXT Ignored. Enclosed content is displayed. PRE Formatted with monospace font. New lines are respected. SELECT TEXTAREA NAME SIZE MULTIPLE NAME ROWS COLs A select list can be a single-selection or a multiple-selection list. A select list contains one or more OPTION elements. With single-selection lists, the OPTION with the SELECTED attribute set is selected by default; otherwise the first option in the list is selected by default. With multiple-selection lists, OPTION elements with the SELECTED attribute set are selected by default; otherwise, no options are selected. A textarea element is rendered as a standard edit field on a single line. It automatically expands vertifically and adds additional lines as text is typed. TITLE Ignored. UL The first enclosed LI element is rendered on separate line. Refer to LI for more information. 58 BlackBerry Browser

59 Acronym list The following table defines acronyms used in this document. Term Definition chtml GIF GPRS HTML HTTP HTTPS IPPP PNG SSL TLS WAP WBMP WTLS WML XHTML XHTML MP Compact HTML Graphic Interchange Format General Packet Radio Service Hypertext Markup Language Hypertext Transport Protocol HTTP over SSL (or TLS) IP Proxy Protocol (used with the BlackBerry Enterprise Server Mobile Data Service) Portable Network Graphics Secure Sockets Layer Transport Layer Security Wireless Application Protocol Wireless Bitmap Wireless Transport Layer Security Wireless Markup Language extensible HTML extensible HTML Mobile Profile

60 Chapter 11: Acronym list 60 BlackBerry Browser

61

62 2002 Research In Motion Limited Produced in Canada