Archive for the ‘Standardisation’ Category

IE6 Countdown: Right time for Browser Standards

Sunday, March 6th, 2011

Its good to see world is ready to move on from Internet Explorer 6. Here is a snippet from IE6 count down site:

10 years ago a browser was born. Its name was Internet Explorer 6.
Now that we’re in 2011, in an era of modern web standards, it’s time to say goodbye.

This website is dedicated to watching Internet Explorer 6 usage drop to less than 1% worldwide, so more websites can choose to drop support for Internet Explorer 6, saving hours of work for web

Internet Explorer 6 usage around the world

Internet Explorer 6 usage around the world

As per my previous post Write Once, use everywhere? Content Vs Code, I think it’s perfect timing to get some standards defined around web browsers.

For corporates, its time to move on and this move is definitely going to give great boost on Intranet front, presenting more opportunities and opening new doors.

Write Once, use everywhere? Content Vs Code

Saturday, March 5th, 2011

One of the thumb rule for any CMS system is:

Have just one instance of the content and define templates/components/modules/elements to render it differently

So, Why the same rule doesn’t apply for code written to define styles, javascript functionality across browsers?

Let me take an example from one of my recent project: As per requirements, we need to support IE (6,7,8), Forefox (3.x), Safari (3.x), Opera (9.x). The HTML mock-ups are generated by one of the creative agency who are in the market for good number of years and know their stuff. SO, just analysing the HTML mock-up, total HTML/CSS/JS size is around 1.9 MB (exclding images). Out of which the CSS/JS specifically for handling cross borwser issues is 0.06 MB which roughly forms 3.5% of the total code set. And such
percentage of cross browser hacking code is present on most of the website.

Below are some of the issues from different perspectives:

Development Perspective

  • Analyse browsers which the site needs to support for previous web analytics or such tools
  • Define graphics which could work across browsers
  • Develop mock-ups with this extra code to hack site working across browsers
  • Testing effort across browsers. Most of the times the UAT error log will have such issues in good percentages
  • More development effort, hence more cost to the project