Linked by Thom Holwerda on Mon 3rd Dec 2012 15:25 UTC
Talk, Rumors, X Versus Y Interesting theory, backed up by data, to explain the difference between Android device sales and browser usage share. "The stock Android browser in previous versions reportedly had problems rendering non-mobile optimized web-pages, leading to lower usage. If a user realized that certain webpages were improperly rendered on a mobile device, it would obviously lead to a drop in future browsing sessions from that device. Meanwhile, on Android 4.0, as consumers have realized that the browsing experience is more "desktop-like", it has led to an increase in browser usage."
Thread beginning with comment 544036
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by shmerl
by lucas_maximus on Mon 3rd Dec 2012 23:11 UTC in reply to "RE[4]: Comment by shmerl"
lucas_maximus
Member since:
2009-08-18

IE didn't try to focus on standards, it tried to hijack them. Luckily it failed.


No, it did try to focus on standards. IE 8 was the first browser that implemented XHTML 1.1 and CSS 2.1 correctly. (Firefox 2 BTW came out at the same time as IE8 and that supported far fewer web standards and has far more bugs).

IE 6 was working against a draft standard at the time and said draft standard was changed after its release and they Microsoft couldn't change it because they promised to support it for as long as they have.

The equivalent browser at the time was Netscape ... and that didn't give f--k about standards.

Also recently, Microsoft have actually been speaking to the web developers on why they don't always support the latest stuff.

This is what I said about it:

http://luke-robbins.co.uk/internet-explorer-and-why-they-are-behind...

Here is the original video:

http://www.youtube.com/watch?v=GvtHb6tBx6Y

The long of the short of it is, that IE is used by the Enterprise and Enterprise customers expect a certain set of features to be support to browser EOL. If they get include standards that aren't finalised they find themselves forever supporting an incorrect standard (see IE6 comment I made above).

I don't think Webkit tries to hijack standards like IE did, but custom extensions obviously complicate things. The situation improves with time though.


No it won't improve with time, because other browser that aren't webkit based are being forced to support the -webkit extensions on mobile.

Webkit it the IE6 of the Mobile browsers.

Edited 2012-12-03 23:15 UTC

Reply Parent Score: 4

RE[6]: Comment by shmerl
by JAlexoid on Mon 3rd Dec 2012 23:34 in reply to "RE[5]: Comment by shmerl"
JAlexoid Member since:
2009-05-19

You sure that you got the dates right?
IE8 released 2009, while FF2 is 2006.

Reply Parent Score: 4

RE[7]: Comment by shmerl
by shmerl on Tue 4th Dec 2012 02:33 in reply to "RE[6]: Comment by shmerl"
shmerl Member since:
2010-06-08

That's the point. Any kind of interest for standards in IE was shown only when Firefox started seriously taking away IE market share. Before that, when IE was too dominating, MS didn't care about standards whatsoever.

Reply Parent Score: 3