Weak point of an otherwise strong phone is definitely the browser

I received my Nokia Oyj. (HEL:NOK1VLumia 900 LTE over the weekend, after initially being informed it was sold out and on back order.  That message appears to have been a mere glitch in AT&T Inc.'s (T) systems.

First let me start by saying that I love my new phone -- it has thus far been a much superior experience to Gingerbread.  I will post my in-depth review shortly, but first I would like to highlight that Microsoft Corp. (MSFT), and co. have some potential issues to address.
I've been busy playing around with the phone over the last few days.  While I did not encounter the dreaded connectivity glitch, but I have been frustrated by the poor quality of the stock browser and some apparent bugs in it, not found in other mobile browsers.

Compared to mobile Safari and mobile Chrome, I would describe the mobile version of Internet Explorer as fast and usable, but difficult.  Admittedly, part of the problem is the learning curve.  After dealing with an icon list to bookmark in mobile Chrome, using the text "Add Favorite", which is a part of a slightly longer list in mobile IE felt more challenging.

More troublingly, the browser seems to be struggling to properly render fonts at their expected sizes on some webpages, including our articles (though the homepage appears to render properly).  While our code clearly defines the font size and the span size for articles, Windows Phone appears to be keeping the font size in pixels, even if the full span size is shrunk via the zoom level.

This seems a clear issue isolated to the mobile Internet Explorer browser.  Text that does not contain pixel size code in their HTML tags appears to be handled correctly and displayed at a reasonable size.

Text rendering bug Text rendering bug
(Highlights added for emphasis. [Image Source: Jason Mick/DailyTech LLC])
The net result is that some items on webpages look huge, when they look small on other mobile browser or on desktop browser (including desktop Internet Explorer 9).

The browser also, auto jumps to the top of the page on some webpages on some websites and scrolling can be jerky.  Both issues interfere with navigating websites.  These issues are not encountered in the mobile versions of Safari, Chrome, Opera, or Firefox.

Yet another ubiquitous issue is that I find that text entered into various Javascript-driven authentication dialogues (text boxes) is not saved -- nor is there an option to save -- forcing you to laboriously type them (username/password/etc.) by hand each time.  Documentation led me to believe it should be saving these kinds of information, but simply isn't.

The "Incognito Browser" does not have the jumping/scrolling bug, plays video, and protects your privacy.  Thus I recommend it as a temporary replacement for Microsoft's fast but very buggy/poor mobile Internet Explorer browser.  Sadly, though, even this option is perfect as the Incognito Browser appears to use the stock rendering engine from IE and still goofs on the text.

Incognito Browser

I am reaching out to representatives at Microsoft and Nokia with regards to these issues.

"Young lady, in this house we obey the laws of thermodynamics!" -- Homer Simpson

Most Popular Articles

Copyright 2018 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki