{"id":7276,"date":"2010-06-25T12:15:41","date_gmt":"2010-06-25T19:15:41","guid":{"rendered":"http:\/\/wapreview.com\/?p=7276"},"modified":"2010-06-25T12:15:41","modified_gmt":"2010-06-25T19:15:41","slug":"samsung-badas-dolfin-browser","status":"publish","type":"post","link":"https:\/\/wapreview.com\/7276\/","title":{"rendered":"Samsung Bada’s Dolfin Browser"},"content":{"rendered":"

$\"Dolfin$ $\"Dolfin$ <\/p>\n

Here’s a look at the capabilities of the Dolfin <\/span>browser on the Samsung Wave <\/span>Bada handset that I got at the Bada Developer Day<\/a> in San Francisco on Tuesday.<\/p>\n

Dolfin is a WebKit based browser.\u00a0 Webkit is used as the basis of the majority of smartphone browsers including those from Nokia, Palm, Android, Apple and soon RIM.\u00a0 Although all these browsers are based on the open source Webkit core, as PPK points out, “There is no Webkit on Mobile”<\/a>, instead there are many mobile Webkit implementations with\u00a0 huge differences between them in usability and rendering.<\/p>\n

I started by running a couple of\u00a0 HTML5 compatibility tests on Dolfin;\u00a0 the W3C’s Web Compatibility Test for Mobile Browsers version 2<\/a> and Momac’s HTML5 Test<\/a>, both of which are comprehensive tests of a large number of HTML5 elements, attributes and JavaScript methods.<\/p>\n

The W3C test has 12 test cases and Dolfin passed nine for a score of 75%.\u00a0 It failed the <video>, <audio> and Web Workers test.\u00a0 By way of comparison, the Android 2.1 browser scored 67% and Opera Mobile 10 passed 34% of the W3C tests.<\/p>\n

Dolfin passed 86 out of 160 of\u00a0 the Momac tests including all parts of the Canvas, Geolocation, Local Storage and Offline Web Application\u00a0 tests.\u00a0 It’s main failure areas were again the lack of\u00a0 support for the\u00a0 Video or Audio elements or Web Workers.\u00a0 The Android 2.1\u00a0 browser scored 118 and Opera Mobile 10\u00a0 only 33 in the Momac test.<\/p>\n

So on paper at least, Dolfin does a pretty good with HTML5 compliance, what of its real world performance and usability? In most areas it’s good.\u00a0 Google delivers the iPhone\/Android HTML5 versions of Search, Gmail, Maps and Calendar to it, all of which worked very well. Google Search and Maps were able to retrieve and use my location.\u00a0 Google Maps (image top, left) is particularly impressive in Dolfin with quick, smooth scrolling and zooming. It’s hard to tell that its not a native app. Google Reader defaulted to the WAP version but I was able to load the iPhone Reader at www.google.com\/reader\/i\/ <\/a>and it worked perfectly too.<\/p>\n

The usability of the Dolfin browser is a bit of a mixed bag.\u00a0 On the positive side, pages seem to load quickly and pinch zooming is exceptionally smooth and accurate.\u00a0 Dolfin doesn’t support “Flick scrolling”,\u00a0 but pages scroll easily by dragging\u00a0 and there is also a scroll bar for quickly getting to a section of the page or to\u00a0 the top or bottom of the screen.\u00a0 A long press on the screen highlights the current word with a drag bar to enlarge the selection and a context menu to copy it, use it as a Google search query or pass it to the mobile web version of Google Translate. Copied text can be pasted into the URL bar or into other apps including email and messaging. Dolfin supports multiple windows although there is no option to open a link in a new window in the background, one of my favorite Android browser features.\u00a0 However, Dolfin tops Android with good support for the HTML <input><\/span> tag’s type=”file”<\/span> attribute which adds a “browse for file” button and dialog to a web page. This feature is used by many file and media sharing sites. File browsing on Bada is limited to your photos, sounds and the Wave’s “others” folder which is a sort of dropbox that you can copy almost any type of file to from a PC using mass storage mode.<\/p>\n

A small thing that I dislike about Dolfin on the Wave is that there is no hardware back button. There’s an onscreen Back icon which is always visible in the browser’s “Normal” screen mode (image top, left).\u00a0 However Normal mode puts large navigation and menu bars at the top and bottom of the screen. The bars can be hidden by choosing “Full Screen” mode but then it takes three taps to go back a page; tapping the screen displays an up arrow icon (image top, right) which you have to tap again to get the menu with the Back icon.<\/p>\n

Unfortunately, JavaScript bookmarklets<\/a> do not work in Dolfin.<\/p>\n

$\"Dolfin$ $\"Dofin$ <\/p>\n

While the Bada Dolfin browser is quite capable and generally performs well, it has one glaring defect that makes it practically unusable for me – when you zoom into a page,\u00a0 text doesn’t reflow<\/span>.\u00a0 That wouldn’t be much of a problem if Dolfin used a readable text size at the default zoom level where columns of text fit the screen width.\u00a0 But on every desktop page I tried, if I double tapped the screen to zoom in on a column of text, the font was impossibly small for reading<\/span>, especially in portrait orientation (image above, left). I could zoom in to get readable text, but then the lines of text became longer than the screen width and required horizontal scrolling<\/span> to read (image above, right), which I consider unacceptable. Things were a little better in landscape orientation, but even there many pages were difficult or impossible to read without zooming to the point where horizontal scrolling became necessary.\u00a0\u00a0 As it is, in spite of\u00a0 its generally good performance, feature set and outstanding stability, I find the Bada browser ultimately unusable because of the text wrapping issue. I strongly suspect that this is an early release bug that I hope Samsung\u00a0 will quickly addresses as it ruins an otherwise outstanding browser.<\/p>\n","protected":false},"excerpt":{"rendered":"