1 <html> |
|
2 <head> |
|
3 <title>Bedrock Browser Release Notes</title> |
|
4 <meta name = "viewport" content = "width = device-width, height = device-height, initial-scale = 1.0, user-scalable = no"> |
|
5 <link rel="stylesheet" type="text/css" href="subpage.css"/> |
|
6 </head> |
|
7 <body> |
|
8 <div id="rel_notes"> |
|
9 <center> |
|
10 <a href="startpage.html"><img src="back.png" height="80" /></a><br/><br/> |
|
11 <h3>Bedrock Browser<br>Alpha 3<br>Release Notes</h3> |
|
12 </center> |
|
13 <br/> |
|
14 <br/><em>Updated: 15-Mar-2010</em> |
|
15 <p> |
|
16 <b>Note:</b> This version of the release notes is current for the software |
|
17 that was packaged at release time. |
|
18 For the latest release notes, visit the Browser Team's Wiki pages. |
|
19 </p> |
|
20 <HR> |
|
21 <h4>Overview</h4> |
|
22 The Bedrock Browser is Nokia's newest web browser. It is based on the latest open-source WebKit |
|
23 engine, and built using the Qt application framework. |
|
24 <p/> |
|
25 The Bedrock project's mission is to provide a fast, easy-to-use, standards-based browser |
|
26 that competes with the best of today's mobile browsers. |
|
27 <p/> |
|
28 In addition to providing basic browser functionality, |
|
29 Bedrock allows for almost infinite extensibility by utilizing an HTML/CSS/JavaScript UI |
|
30 (User Interface) framework called "Ginebra". |
|
31 <p/> |
|
32 All of the UI components you see in the Bedrock Browser are rendered using Ginebra. |
|
33 The UI can be modified as easily as modifying a web page. |
|
34 <p/> |
|
35 <HR> |
|
36 <h4>About this Release</h4> |
|
37 This is the Alpha 3 release of Bedrock. This release has been enhanced since the Alpha 2 release. |
|
38 However, the set of functionalities is currently limited. |
|
39 <P/> |
|
40 Additionally, while performance has also significantly improved, |
|
41 it has not yet reached the desired level. |
|
42 <p/> |
|
43 Please review the following Release Notes and provide your input on this release |
|
44 by using the feedback mechanisms on the Backstage site. |
|
45 <P/> |
|
46 |
|
47 <HR> |
|
48 <h4>Target Platforms and Devices</h4> |
|
49 The Bedrock Browser is released as a signed SIS package that can be installed on N97 devices. |
|
50 We recommend using a CE device with the latest firmware patches, as opposed to an R & D prototype device. |
|
51 <P/> |
|
52 <HR> |
|
53 <h4>Prerequisites</h4> |
|
54 The Bedrock Release requires the following: |
|
55 <ul> |
|
56 <li>A Nokia N97 device, consumer version (CE) recommended. |
|
57 (If you use this release on an R & D prototype device, it is at your own risk.)</li> |
|
58 <li>The latest platform software installed on the device. |
|
59 This release has been tested with: N97 Software Version 12.0.024, dated 04/08/09</li> |
|
60 <li>You must install all of the provided software packages on your device's C: drive.</li> |
|
61 <li>You need a minimum of 11-12 MB of free space on the C: drive. |
|
62 (HINT: Open the platform browser and clear the device's browser cache - this will free up a few MB.</li> |
|
63 <li>If your device has a previously-installed version of the Bedrock browser or the Qt framework, |
|
64 you must remove them before proceeding. |
|
65 Please review the installation notes for information about removing older components |
|
66 from your device.</li> |
|
67 <li>The default network setup is required on the device. |
|
68 The N97 connection settings must contain the default <em>Destination Network</em> of <em>"Internet"</em> |
|
69 that contains the proper access points (APs). |
|
70 The browser will connect to the network using this Internet Destination Network. |
|
71 <br> |
|
72 <B>Important:</B> Ensure that the default access point |
|
73 (as defined in the connection settings for the Destination Network) |
|
74 is available when running the Bedrock browser. |
|
75 There have been cases where an unavailable WLAN AP prevented loading of pages. </li> |
|
76 </ul> |
|
77 |
|
78 <HR> |
|
79 <h4>Functionality to Evaluate</h4> |
|
80 We encourage you to try out the following new features and let us know what you think! |
|
81 <ul> |
|
82 <li>Zooming: |
|
83 <ul> |
|
84 <li>Basic incremental zoom-in/zoom-out is available with the two zoom buttons on the lower toolbar.</li> |
|
85 <li>Double-tap "fit-to-block" zooming will zoom/focus in on a block of text or an image. |
|
86 <br>Also, please try to give us feedback on Zooming out using a double-tap gesture.</li></ul> </li> |
|
87 <li>Viewport scaling: The browser now supports the meta tag options for setting the viewport |
|
88 (display area) for the web page. See "Known Limitations" section for limitations/impacts. |
|
89 Google "meta viewport" for details on this feature. If you know of sites that use this feature, |
|
90 please try them with the browser.</li> |
|
91 <li>Windows View: Tap the "Windows" button on the toolbar to open the windows manager and add a new window. |
|
92 Then, return to switch between windows.</li> |
|
93 <li>GoToAnywhere View: Now includes Bookmarks, History, and Visual History. |
|
94 Try adding a bookmark (it will add a bookmark to the current page in the content view).</li> |
|
95 <li>Session Restore: The browser will restore the previous session, including session history, |
|
96 in each of any open windows. Try opening multiple windows and browsing multiple pages in each. |
|
97 Then, exit the browser (red "end" key) and launch the browser again. |
|
98 All of your windows and history should be restored!</li> |
|
99 <li>Standards Tests: The WebKit engine in this release has been updated |
|
100 and is now doing a much better job on standards tests (like ACID3).</li> |
|
101 <li>Navi-key scrolling: The 4-way navi-key and middle "Select" key can now be used to scroll the page |
|
102 and select items.</li> |
|
103 </ul> |
|
104 <HR> |
|
105 <h4>Known Limitations</h4> |
|
106 <ul> |
|
107 <li>WebKit Performance: Although improved, there are a number of known issues with |
|
108 the Qt WebKit used in this release of Bedrock. Some have a major impact on performance of the engine. |
|
109 For example, rendering after a zoom-level change is known to be slow. See our wiki page for more details.</li> |
|
110 <li>Out of Memory Handling: Handling of low memory conditions is not yet optimized for browsing large web pages. |
|
111 In some cases, loading large or image-intensive pages can cause the browser to lock-up or crash. |
|
112 Please report the sites/pages to us if you experience this.</li> |
|
113 <li>UI Performance: We are still evaluating and responding to performance issues. |
|
114 When using this Alpha release, please be patient when performing actions. |
|
115 Avoid quickly repeating actions if it seems there is a lack of response to an action. |
|
116 Once a button or link is pressed, or a touch gesture is applied, |
|
117 it may take some time for the resulting action to be reflected in the UI. |
|
118 However, sometimes touch gestures are "lost" and you may need to repeat them to activate a control.</li> |
|
119 <li>Adding a new window: When adding a new "blank" window from the Windows View, |
|
120 the browser may (incorrectly) restore a previously open window instead of creating a new, blank window.</li> |
|
121 <li>Restoring Session: When launching the browser the previously open windows and pages will be restored. |
|
122 If the pages that were previously open were large or in some way problematic for the browser, |
|
123 restoring the session might restore those problems as well. |
|
124 If any strange behavior is seen when restoring the last session, |
|
125 try closing as many windows as possible and ensure that each window contains a "simple" page |
|
126 (like Google's search page).</li> |
|
127 <li>Changing the browser orientation from landscape to portrait and vice-versa is better supported now, |
|
128 but there are some known issues. For example, in any view that shows a page thumbnail, |
|
129 that thumbnail is not updated to reflect the orientation change. |
|
130 Also, entering text in portrait mode is "undefined" at this time - any virtual keyboard that might |
|
131 come up has not been fully tested in that mode. We recommend using the hardware keyboard for text entry.</li> |
|
132 <li>Form input password fields: Character hiding IS supported when entering a password into a form field, |
|
133 but this is actually problematic. Because no "preview" of the typed character is provided, |
|
134 it is not possible to verify the character typed. Be sure you have the proper text entry mode |
|
135 (lower case, all caps, mixed) set before entering a password.</li> |
|
136 <li>Secure page indication is now supported, but the indicator may not refresh properly |
|
137 when switching between windows or moving back through history.</li> |
|
138 <li>HTTP authentication is supported but the masking of the characters |
|
139 as the password is entered is not yet enabled. |
|
140 Also, the HTTP authentication dialog has no "OK" button. |
|
141 Press the hardware Enter key to submit the authentication.</li> |
|
142 <li>Form field input masking is not yet supported. |
|
143 This can cause some form entry use cases to fail if the data entered is not formatted correctly.</li> |
|
144 <li>Text Prediction / T9 Issues: Please be sure that when entering any text into any edit field |
|
145 (especially the URL entry box!) that text prediction is turned OFF.</li> |
|
146 <li>Viewport scaling is supported but in some cases will result in pages that are "clipped" |
|
147 vertically on the page. If pages are not rendered properly (you can sometimes "see" |
|
148 the previous page "under" the offending page) try changing the zoom level.</li> |
|
149 <li>File downloading is NOT yet supported. If you attempt to load content that |
|
150 isn't rendered in the browser itself, it will NOT be downloaded. |
|
151 So, for example, clicking a link to another HTML page will load/render that page. |
|
152 Clicking a link to a JPG image will load that image into a page in the browser. |
|
153 But clicking a link to a PDF, MP3, ZIP or other type of content file will not result in a download. |
|
154 Nothing will happen.</li> |
|
155 <li>File uploading via the HTML form <input type="file"... mechanism is NOT supported.</li> |
|
156 <li>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.</li> |
|
157 </ul> |
|
158 <HR> |
|
159 </div> |
|
160 </body> |
|
161 </html> |
|
162 |
|