Release Notes for
- Bedrock Browser TRUNK VERSION
+ Nokia Browser 8.0 TRUNK VERSION
- Updated: 25-May-2010
+ Updated: 2-Jun-2010
NOTE: These release notes are for TRUNK version releases ONLY. When branched for final release, a final set of release notes will be replace this file.
NOTE: These release notes were current as of the time the software was packaged for release. For up-to-date release notes, visit the Browser Team's Wiki pages.
Overview of the Release:
-
The Bedrock Browser is Nokia's latest web browser based on the latest open-source WebKit
+
The Nokia Browser is Nokia's latest web browser based on the latest open-source WebKit
engine and built using the Qt application framework.
-
The Bedrock project's mission is to provide a fast, easy to use, web-standards based browser
+
The Nokia ASF Browser project's mission is to provide a fast, easy to use, web-standards based browser
that can compete alongside the best of the mobile browsers.
-
This release of Bedrock is the Alpha 3 release. While the functionality has certainly has been enhanced
+
This is the Alpha 4 release of the Nokia Browser. While the functionality has certainly has been enhanced
since the Alpha 1 and 2 releases (which were released to a very limited audience) and the performance has also been improved significantly,
the performance is still behind where we want and need it to be.
Please review the rest of the Release Notes and provide feedback on this release via the feedback mechanisms on the Backstage site.
Target Platforms/Devices:
-
The Bedrock Browser is released as a signed SIS package that can be installed on N97 devices. We recommend using a CE device with the latest
+
The Nokia Browser is released as a signed SIS package that can be installed on N97 devices. We recommend using a CE device with the latest
firmware patches as opposed to an R&D / prototype devices.
Prerequisites:
@@ -54,7 +54,7 @@
NOTE: It is required for this release that you install ALL of the provided software packages on the C: drive.
NOTE: If you had previously installed the Alpha 1 release OR any version of the Qt framework, please review the installation notes carefully and remove older components from your device as directed..
Default network setup on the device. The N97 connection settings must contain a default Destination Network of "Internet" that contains the proper access points (APs). The browser will connect to the network via this "Internet" Destination Network.
-
IMPORTANT: Ensure that the default access point (as defined in the connection settings for the Destination Network) is available when running the Bedrock browser. There have been cases where an unavailable WLAN AP prevented loading of pages.
+
IMPORTANT: Ensure that the default access point (as defined in the connection settings for the Destination Network) is available when running the browser. There have been cases where an unavailable WLAN AP prevented loading of pages.
Functionality to Evaluate:
The following features are a few we encourage you to try out!
@@ -75,7 +75,7 @@
Known Limitations:
-
WebKit Performance: Although improved, there are a number of known issues with the Qt WebKit used in the release of Bedrock. Some have a major impact on performance of the engine. For example, rendering after a zoom-level change is known to be slow. See our wiki page for more details.
+
WebKit Performance: Although improved, there are a number of known issues with the Qt WebKit used in the release of the Browser. Some have a major impact on performance of the engine. For example, rendering after a zoom-level change is known to be slow. See our wiki page for more details.
Out of Memory Handling: Handling of low memory conditions is not yet optimized for browsing large web pages. In some case, loading large or image-intensive pages can cause the browser to lock-up or crash. Please report the sites/pages to us if you experience this.
UI Performance: We are still evaluating and responding to performance issues. When using this Alpha release, please be patient when performing actions. Avoid repeating the same actions quickly in response to a lack of response. Once a button or link is pressed or a touch gesture is applied, it may take some time for the resulting action to be reflected in the UI. Also, sometimes touch gestures are "lost" and you may need to repeat them to activate the control.
@@ -100,6 +100,10 @@
The URL entry bar is now designed to "scroll off" the top of the view when the page is scrolled up. It has been noticed that sometimes the bar will not re-display after scrolling back up.
