(Difference between revisions)

Symbian Browser and Web Runtime 7.3 for Developers

From Nokia Developer Wiki
Jump to: navigation, search
petrosoi (Talk | contribs)
hamishwillee (Talk | contribs)
m (JavaScript execution change: - change to use wiki internal link format)
Line 119: Line 119:
//continue by using old per service permission model
//continue by using old per service permission model
===JavaScript execution change===
[[Category:Symbian Web Runtime]]
[[Category:Symbian Web Runtime]]
===JavaScript execution change===
[[KIS001646 - JavaScript execution change in Browser 7.3 on Symbian devices]]

Revision as of 06:08, 19 April 2011


Target devices

Symbian Browser and Web Runtime discussion boards

Web Development at Forum Nokia discussion boards

User Agent string

User agent string structure

Mozilla/5.0 (OSName/OSVersion; U; DeviceModel/DeviceSoftwareVersion) WebEngineType/WebEngineversion (KHTML, like Gecko) BrowserName/BrowserVersion Mobile Safari/WebKitversion

Example: N8

Mozilla/5.0 (Symbian/3; Series60/5.2 NokiaN8-00/012.002; Profile/MIDP-2.1 Configuration/CLDC-1.1 ) AppleWebKit/533.4 (KHTML, like Gecko) NokiaBrowser/7.3.0 Mobile Safari/533.4 3gpp-gba

Targeting Symbian Browser 7.3 with cross platform web content

The Symbian WebKit port update brings substantial performance and feature compatibility upgrades to e.g. content rendering.

Web content providers are in many cases well of by serving content optimized for other smartphone platforms to Symbian Anna devices.

However, when fine graining application behavior, there are several things developers must keep in mind when supporting Symbian Anna.

Below is a list of the most commonly encountered differences to other WebKit based smartphone browsers:

  • The only reliable user interaction event is the single click
    • touch* events and advanced gestures are not supported
  • No device API access (e.g. GeoLocation or accelerometer) from browser context
  • No HTML5 video or audio support
  • CSS3 animations, transforms and transitions may have performance issues, especially with complex content

VGA resolution

The Nokia E6 introduces VGA resolution (640 x 480px) with a very high pixel density (screen size is 2.4 inches)

Until now, Symbian^3 devices and Series 60 5th edition devices have shared a common screen resolutionof 640 x 360px.

Greater pixel density leads to situation where touchable elements should be a lot bigger in terms of pixel size to be usable. For example the smallest touchable element should be 7 x 7mm. On N8 this is about 60 x 60px, but to get similar dimensions in E6you would need to have an element sized 90 x 90px.

The VGA resolution menu bar height is 54px and the display is fixed to landscape mode.

VGA landscape.png

New and updated features for developers

Updated WebKit

Symbian WebKit port has been updated (v533.4). The update brings significant performance and compatibility benefits, compared to earlier Symbian browsers.

As a benefit of the updates to Symbian WebKit the underlying graphics adaptation layer, several CSS3 visual elements and effects , including 2D transforms, rounded corners and gradients, are at least partially supported.

In addition to these developers can utilize CSS media queries and viewport meta tags available e.g. in iOS and Android browsers.


Support for a small subset of HTML5 features, including the doctype, section-level markup tags, form input attributes, placeholder text attributes for input fields, the scrollintoview method, and the contenteditable attribute.

Offline capabilities (web storage, application cache), HTML5 audio/video and HTML5 geolocation are not supported.


Support for a subset of CSS3 features, including animation, backgrounds, borders, color, gradients, media queries, multi-column layout, selectors, text effects, transitions, and 2–D transforms.

DPI based scaling

Browser 7.3 introduces a mechanism to enhance readability on devices with high pixel density screens.

160 DPI is treated as a default value, meaning that content will be scaled to 100%, whereas e.g. N8 (22 DPI) and E6 (330 DPI) will get scaling factors 1.25 and 1.50 respectively.

Note: this change exists only in the browser context so existing WRT widgets are not affected

Note: Developers should utilize the viewport meta tag, just introduced to Symbian Browser 7.3, to explicitly control scaling of the web content served through the browser.

Web Runtime Homescreen dimensions

Observed Home Screen widget size stays unaffected to keep the compatibility with N8 or N97 i.e. 312x82px.

The actual resolution of the home screen widget slot is 440 x 116px on a VGA device.

The home screen widget image is automatically scaled to fit the available resolution.

Old code for detecting if widget is shown on home screen, can still be used without modifications, because Web Runtime reports window.innerHeight as 82px instead of actual 116px.

Renewed WRT security prompts

WRT 7.3 supports a new API group all of the platform service (device API) permission prompts into a single prompt. Hence the end user doesn’t have to allow use of platform services APIs one by one during the application usage.

The new API is part of the device-object.

device.getServicePermissions( requestedServices)

RequestedServices is an object which holds the names of the services that are used by the widget. The service provider’s name is used as an object’s property name and interface name as its value.

//check for getServicePermissions for backward comptibility	
if(device && typeof device.getServicePermissions == "function"){
try {
"Service.AppManager": "IAppManager",
"Service.Calendar": "IDataSource",
"Service.Contact": "IDataSource"
catch (e) {
//notify the user that access to services has been declined
//continue by using old per service permission model

JavaScript execution change

KIS001646 - JavaScript execution change in Browser 7.3 on Symbian devices

215 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.