WebSettings

This processing takes place immediately after any document load completes; it is expensive.

The default is false.

If you wish to enable controls behind the WebView to appear through the webpage, you must set a non-opaque color.

The default is opaque white.

The default is true.

The default is true.

The default is false, setting to this to true can reduce the amount of times the user is prompted for credentials.

Each key value pair in the map will be converted to UTF8 strings and added to outgoing requests as "<key>: <value>".

WebView {
    url: "http://myserver.mynetwork.net/anycontent.html"
    settings.customHttpHeaders: { "Pragma": "no-cache" }
}

The default is 16.

Any value set using the defaultFontSize property will be ignored while this setting is true.

If your web content uses relative font sizes, like em or %, enabling this setting will allow the user to control the font size of your content using the system font size setting.

Please note that the textAutosizingEnabled feature already accounts for system font size, so it's not recommended to have both defaultFontSizeFollowsSystemFontSize and textAutosizingEnabled simultaneously set to true.

The default is false.

The default is ISO-8859-1.

The devicePixelRatio is the ratio between physical pixels and device-independent pixels (CSS pixels) on the device.

Increasing devicePixelRatio will zoom in the content and decreasing it will zoom out the content.

Beyond the devicePixelRatio, which scales the very CSS pixels of the web page, the web content can also be scaled due to zoomToFitEnabled being set to true. An "initial-scale" viewport argument present on the web page or injected using the viewport property can also influence scaling. The "initial-scale" is a multiplier applied in addition to the devicePixelRatio.

There are two approaches to scaling your web content.

Use the default devicePixelRatio to optimize for a mix of desktop and mobile web content. Typically, the default value is appropriate for loading existing web content from the world wide web. At the default devicePixelRatio, a font size of ~16 CSS pixels is pleasant to read. The user may adjust the system font size setting if they prefer bigger or smaller text, and the textAutosizingEnabled feature (enabled by default) takes the system font size setting into account when adjusting font size for improved readability. Enabling defaultFontSizeFollowsSystemFontSize is not recommended in this scenario.

Use a devicePixelRatio of 1.0 and tailor your web content to fit the standard screen width of BlackBerry 10 devices. Typically, a value of 1.0 is used when the web content is created specifically for BlackBerry 10 devices. At this devicePixelRatio, a font size of ~40 CSS pixels is pleasant to read, but you can enable defaultFontSizeFollowsSystemFontSize to have the default font size be adjusted to exactly match the system font size setting. When using a devicePixelRatio of 1.0, defaultFontSizeFollowsSystemFontSize is recommended over the textAutosizingEnabled feature. The text autosizing algorithm can't properly adjust font sizes without an accurate devicePixelRatio value.

The default is false, setting to true can reduce the amount of input the user needs to type.

The default is true.

The default is true.

The default is 8.

Web content designed for desktop web browsers can contain text too small to be readable when the column of text is zoomed to fit the screen width. Text autosizing improves the situation by adjusting font size of text depending on column width and the screen's pixel density (DPI). If the user has changed the system font size setting, the effects of the text autosizing algorithm will be attenuated (if system font size is smaller than the default setting) or magnified (if the system font size is greater) to accommodate the user's setting.

This means that the text autosizing feature already accounts for system font size, so it's not recommended to have both defaultFontSizeFollowsSystemFontSize and textAutosizingEnabled simultaneously set to true.

To determine the scaling required, the text autosizing algorithm depends on the devicePixelRatio, so autosizing works best if devicePixelRatio is left at it's default value. Setting devicePixelRatio to 1.0 effectively disables autosizing.

The default is true.

The default is the same as the userAgent employed by the BlackBerry Browser; it depends on the form factor and operating system version present on the device.

The default is an empty URL, which indicates that there is no user style sheet.

This map can be assigned a series of key value pairs from the following sets:

The following case-sensitive strings are accepted as keys: { "initial-scale", "minimum-scale", "maximum-scale", "width", "height", "user-scalable" }

The "initial-scale" is a multiplier applied in addition to the devicePixelRatio.

The following case-sensitive strings are accepted for all viewport values though not all of them are necessarily useful for each property: { "auto", "desktop-width", "device-width", "device-height" }

In addition, any non-negative floating point values are also acceptable.

To set a common type of meta viewport tag that requests that the content be laid out to the screen width in the current orientation, and zoomed 1:1, use this:

The default is an empty map which indicates no user specified viewport meta tag should be used.

WebView {
    id: webView
    url: "http://myserver.mynetwork.net/anycontent.html"
    settings.viewport: { "initial-scale" : 1.0 }
}

The default is false. The WebInspector is specifically for debugging and should never be enabled in released software.

The default is true.