David Walker | 7 December 2012
The launch of Windows 8 saw the arrival of Internet Explorer 10 and with it the true dawn of the HTML5 age. With Microsoft’s excellent implementation of the core HTML5 and CSS3 functionality we have arrived at a point in web development where the current release of every major web browser is HTML5 ready.
This ground-breaking moment means as a web developer I can begin to look at my beloved HTML5 as the norm and not the bleeding edge it was when I tentatively wrote my first <section> tag two years ago. It means the original WHATWG standard is now mostly accepted in browsers, although not all features are W3 Recommendations yet.
It is also part of the big Microsoft Windows 8 plan to rehabilitate themselves and bad practices they gave rise to on the web. Yes IE did suck, Microsoft recognize this and no amount of bombastic adverts in the Cinema telling us IE9 was the future of the web can ever take away from the cry "IE SUCKS!" because, well...it did terribly! I could give you a hundred examples of the issues but Microsoft have realised how bad their rep was.
From the outside designers get very frustrated that organisations do not upgrade to the most recent version of a browser as soon as it is released. The problem is, many of these old browser issues have been hacked around over many years to get an intranet to work. Plus if you are still on XP as your corporate OS then you can't upgrade past IE8 and that means unless a developer is willing to support you (they should but time constraints and budgets cause some key issues). Organisations with robust security policies based over multiple locations cannot upgrade and cannot allow an alternative browser like Firefox or Chrome because they don't play ball with the Active Directory security model in quite the same way.