MyMobileWeb: WURFL Capabilities
From Morfeo Wiki
Properties used by MyMobileWeb
| WURFL | ||
| Group: product_info | ||
| Capability Name | Type | Description |
| brand_name | string | Brand |
| model_name | string | Model |
| is_wireless_device | true/false | Tells you if a device is wireless or not. Specifically a mobile phone or a PDA are considered wireless devices, a desktop PC or a laptop are not |
| has_pointing_device | true/false | The presence of a stylus is the tipical example of this, but there are also devices with mouse-like user controls that can have this capability set to true.In general, not having to click your way to each and every link (or form widget) makes a big difference and this capability captures that. |
| can_skip_aligned_link_row | true/false | Many modern devices (or browser/device combo) let users skip a row of links (for ex: link1|link2|link3|link4) with just one click down. Other devices force users to click multiple times to skip the list of links. |
| Group: wml_ui | ||
| Capability Name | Type | Description |
| built_in_back_button_support | true/false | User may always click on a button to go back |
| card_title_support | true/false | The device displays the title on the screen |
| softkey_support | true/false | Softkeys are supported |
| table_support | true/false | The browser displays tables formatted "correctly" (rather than 1 cell per line) |
| menu_with_select_element_ recommended | true/false | A select element is the most usable menu format |
| break_list_of_links_with _br_element_recommended | true/false | When presenting a list of links the use of <br/> is suggested for better presentation |
| access_key_support | true/false | Respects the "accesskey" attribute of the anchor tag |
| image_as_link_support | true/false | You may use images to present a link |
| insert_br_element_ after_widget_recommended | true/false | The use of a break is suggested after widgets |
| opwv_wml_extensions_support | true/false | This is specific for Openwave browsers and possibly third party browsers that are compatible. As WML extensions we mean pictograms and other tags that were never formalized by the WAP forum |
| wml_make_phone_call_string | string | Prefix to initiate a voice call |
| Group: chtml_ui | ||
| Capability Name | Type | Description |
| chtml_table_support | true/false | Tables are not supported by default on i-mode/chtml devices. This capability tells you if the device supports this "extra" feature |
| imode_region | string | This field describes the market region for the device, useful for emoji's and other possible localizations. Possible values as "ja" for Japan, "eu" for Europe, "us" for USA "as" for Asia. "none" means unknown or not set. |
| emoji | true/false | Emoji are special characters which appear in i-Mode pages as small icons |
| chtml_make_phone_call_string | string | Prefix to initiate a voice call |
| Group: xhtml_ui | ||
| Capability Name | Type | Description |
| xhtmlmp_preferred_mime_type | string | Most devices should support both text/html and the specific XHTML MP mime type. Some are a little pickie, here you should find a mime type that always works. Default is text/html |
| xhtml_document_title_support | true/false | While one can define the document title with the title tag, not all devices actually render the title. This capability keeps track of that behavior |
| xhtml_supports_table_for_layout | true/false | This device support for tables is solid enough that you can use tables to layout content on the screen. |
| xhtml_table_support | true/false | Tables should be supported as syntax, but are often rendered poorly. This tag tells you if the browser is able to render tables decently |
| xhtml_allows_disabled_ form_elements | true/false | XHTML lets you define "disabled" form elements. If this actually works on the different devices is tracked down by this capability. |
| xhtml_display_accesskey | true/false | The device displays a number when you use an accesskey |
| xhtml_marquee_as_css_property | true/false | Does device support MARQUEE though CSS syntax? |
| xhtml_readable_background_color1 | string | This and the following properties lets you define 2 colors which interoperate visually on the device. For example, by using one of these two colors as background, you don't risk that an hyperlink disappears against its background. |
| xhtml_readable_background_color2 | string | Refer to xhtml_readable_background_ color1 for description |
| opwv_xhtml_extensions_support | true/false | The Openwave browser has some supports some useful extensions. |
| xhtml_preferred_charset | string | UTF-8 should be supported by default, but some devices have problems. Here you may find alternative charsets such as iso8859. This field does not present the exact charset because with ISO charsets you may need to specify the one of your region (1, 15, other) |
| xhtml_select_as_radiobutton | true/false | The device displays select's as radio buttons |
| xhtml_format_as_css_property | true/false | This field is true if the device supports a css property to define the format of an input field. This is what the "format" attribute was in WML. Follows the same rules as "format" used to do. |
| xhtml_format_as_attribute | true/false | This is set true if the device supports the "format" attribute in input fields |
| xhtml_nowrap_mode | true/false | Does device support wrap mode as a XHTML attribute? |
| xhtml_make_phone_call_string | string | Prefix to initiate a voice call |
| xhtml_supports_file_upload | true/false | Supports input tag with file type |
| Group: markup | ||
| Capability Name | Type | Description |
| preferred_markup | string | This field identifies which markup is best supported by the device. This field is filled on personal experiences of our contributors. Values for this capability look like: wml_1_1, html_wi_imode_compact_ generic and html_wi_oma_xhtmlmp_1_0. |
| html_web_4_0 | true/false | Supports HTML version 4 |
| Group: display | ||
| Capability Name | Type | Description |
| max_image_width | any integer number | Width of the images viewable width expressed in pixels |
| max_image_height | any integer number | Height of the images viewable width expressed in pixels |
| resolution_width | any integer number | This field represents the display's usable width expressed in pixels |
| resolution_height | any integer number | This field represents the display's usable height width expressed in pixels |
| columns | any integer number | Number of columns presented |
| rows | any integer number | Number of lines presented |
| Group: image_format | ||
| Capability Name | Type | Description |
| wbmp | true/false | Supports wbmp format |
| bmp | true/false | Supports bmp format |
| gif | true/false | Supports gif format |
| jpg | true/false | Supports jpg format |
| png | true/false | Supports png format |
| svgt_1_1 | true/false | Supports SVGT v1.1 |
| colors | any integer number | In general the number of colors used by the phone |
| Group: bugs | ||
| Capability Name | Type | Description |
| emptyok | true/false | An empty select is allowed |
| empty_option_value_support | true/false | If true the phone will allow the user to pick an empty value from a select |
| Group: wta | ||
| nokia_voice_call | true/false | Supports the Nokia 'make call' function |
| wta_voice_call | true/false | Supports the standard WML call function |
| Group: storage | ||
| Capability Name | Type | Description |
| max_deck_size | any integer number | Maximum allowed size for a deck in bytes |
| max_object_size | any integer number | The maximum filesize supported when downloading using WTP-SAR |
The extensions provided by MyMobileWeb
- MyMobileWeb adds some capabilities on its own to the standard WURFL catalogue. They are needed for components of multidevice adaptation that form part of the MyMobileWeb product. In the following table these capabilities are described.
| MyMobileWeb | ||
| Group: xhtml_ui | ||
| Capability Name | Type | Description |
| xhtml_align_center_ insert_auto_br | true/false | The browser inserts a br between tags with align center |
| xhtml_insert_br_after_ input_with_nowrap | true/false | It points out whether a new line tag must be written after a input data tag with nowrap style |
| xhtml_insert_br_after_select | true/false | It points out whether a new line tag must be written after a select tag displayed as a combo |
| xhtml_nowrap_mode_in_table | true/false | Supports nowrap mode in table |
| xhtml_url_encoded | true/false | Must be encoded the url |
| Group: browser | ||
| Capability Name | Type | Description |
| cookie_support | true/false | Does the browser support cookies? |
| javascript_support | true/false | Does the browser support Javascript? |
| external_script_support | true/false | Is the fact that the script code was located outside the HTML page supported by the browser? |
| Group: bugs | ||
| Capability Name | Type | Description |
| empty_text_value_not_ sent_in_request | true/false | Is empty text values sent in request? |
| Group: sms | ||
| Capability Name | Type | Description |
| can_send_sms_from_browser | true/false | Supports to send sms from browser |
| Group: markup | ||
| Capability Name | Type | Description |
| html_wi_w3_xhtmlbasic_1_1 | true/false | Supports XHTML Basic 1.1 |
| html_wi_oma_xhtmlmp_1_2 | true/false | Supports XHTML MP 1.2 |