http://www.engadgetmobile.com/2008/05/30/about-that-samsung-l870-safari-browser-thing/ Engadget Mobile Comments for About that Samsung L870 Safari browser thing... http://www.engadgetmobile.com/media/feedlogo.gif http://www.engadgetmobile.com en-us Copyright 2009 Weblogs, Inc. The contents of this feed are available for non-commercial use only. Blogsmith http://www.blogsmith.com/http://www.engadgetmobile.com/2008/05/30/about-that-samsung-l870-safari-browser-thing/http://www.engadgetmobile.com/2008/05/30/about-that-samsung-l870-safari-browser-thing/
you know, when there wasn't other browser called mobile safari]]>May 30th 2008 10:14AMhttp://www.engadgetmobile.com/2008/05/30/about-that-samsung-l870-safari-browser-thing/http://www.engadgetmobile.com/2008/05/30/about-that-samsung-l870-safari-browser-thing/
Yes, it uses Apple's WebKit (formerly KHTML) for rendering. IE uses code inherited from NCSA Mosaic, as does (to a lesser degree) Firefox. And Apache ("a patchy" web server) for that matter.

They probably based their assertion on the "User-Agent" string; my N95 sends the following "User-Agent:" header:

Mozilla/5.0 (SymbianOS/9.2; U; Series60/3.1 Nokia N95_8GB-3/20.2.005 Profile/MIDP-2.0 Configuration/CLDC-1.1 ) AppleWebKit/413 (KHTML, like Gecko) Safari/413

Such user agent strings are notoriously misleading for many reasons. (For one, various statistics about phone data plan usage tend to count access from these S60 browsers as iPhone use...). This browser, though, is neither Mozilla, Konqueror (as KHTML would indicate), or Safari.

It would also seem that Samsung might have another issue with calling this Safari, since Safari is a trademark owned by Apple.

]]>May 30th 2008 3:59PMhttp://www.engadgetmobile.com/2008/05/30/about-that-samsung-l870-safari-browser-thing/http://www.engadgetmobile.com/2008/05/30/about-that-samsung-l870-safari-browser-thing/Jun 1st 2008 8:14PM