Linked by Thom Holwerda on Tue 15th Mar 2011 18:17 UTC, submitted by gogothebee
Internet Explorer Yes, yes, yes - that's what you get for releasing Internet Explorer 9 in the middle of the night, Microsoft! A post on OSNews that's late! I'm sure that'll teach you. Anywho, as you may have noticed, Microsoft is back in the browser game - Internet Explorer 9 has been released.
Thread beginning with comment 466285
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Not going back
by lemur2 on Tue 15th Mar 2011 21:52 UTC in reply to "RE: Not going back"
Member since:

As for other browser such as Chrome, Safari etc, I am already seeing the IE6 effect in the mobile space (and the lesser effect desktop space) with devs targeting Webkit and letting other browsers suffer in the name of progressive enhancement.

Nitpick ... in some markets Firefox is the most used browser.

Worldwide and in just about every individual market, Firefox has a much larger share than webkit browsers.

Given these facts, why wouldn't a developer target gecko (Firefox) first, and then enjoy the fact that other browsers such as Chrome and Safari useing webkit, or IE9 for that matter, should also work.

OK, IE9 might still be a little way off, but it won't be too bad.

After developing your website targetting Firefox, if you then get any complaints from Windows XP users, just tell them to install and run either Firefox, Chrome, Opera or Safari.

Reply Parent Score: 4

RE[3]: Not going back
by lucas_maximus on Wed 16th Mar 2011 09:23 in reply to "RE[2]: Not going back"
lucas_maximus Member since:

It is because Webkit is most prevelent on smart phones.

Mobile websites use something like WURFL/WALL to detect the devices capabilities (think User Agent Sniffing on steroids) or worse they use some sort of basic user agent sniffing (does the user agent contain the word iPhone) ... this can be client side or server side.

Ideally you need a combination of at least three technologies, WUFZL or equivalent to detect what the device can do, Server side logic to serve the correct content. Client side detection of its abilities i.e. video tag etc, geolocation via the browser ...

However It is easier for Devs to split this to Webkit/Smartphone and "everything else", this is the feedback I have got from working with various companies that specialise in Mobile dev.

Edited 2011-03-16 09:30 UTC

Reply Parent Score: 2