That dreaded IE6… [#2]


Yesterday I made a post regarding that fakap IE6. Which is Web-Developers worst nightmares on earth. My nightmare. IE6 is the dying old man which refuses to retire. So I wrote a little script to force users to upgrade whenever they view the library portal.

However, after looking at the log files and google anal. report, I soon realize that forcing users to upgrade their browser is mean. So mean, to the extend that some users still stump upon the upgrade warning. (lol. they still asked me what to do). I do so believe the warning is so direct. Why some users still don’t get it.

Some users may not upgrade to the latest IE due to unlicensed copy of Windows (stop using pirated windows ler). Some users may not install alternative browsers due to Company Restrictions (what company is that… so evil). Due to this I will have to lift the force upgrade script.

So… once again hacks and workaround will do the trick. All this started with CSS compatibility issues. Some elements may not appear in IE6 and some element will break the page in IE6. Sometimes I will have to forget the beautiful effect and design since in IE6 the page will break. What a nuisance.

After searching for solutions how to these pages at least viewable in IE6 I come across the conditional codes. Hmm. Created by Microsoft for Internet Explorers.

One of the most common operations performed in a Web page is to detect the browser type and version. Browser detection is performed to ensure that the content presented to the browser is compatible and renders correctly. The browser type can be detected using many different techniques. Most methods of browser detection make use of script on the server or client.

This article introduces conditional comments, which offer certain advantages over scripted browser detection techniques. Conditional comments make it easy for developers to take advantage of the enhanced features offered by Microsoft Internet Explorer 5 and later versions, while writing pages that downgrade gracefully in less-capable browsers or display correctly in browsers other than Windows Internet Explorer. Conditional comments are the preferred means of differentiating Cascading Style Sheets (CSS) rules intended for specific versions of Internet Explorer.

Source :

After some reading I use these stupid IE codes

 <!--[if lte IE 6 ]><div id="bodoh"><![endif]-->
 <!--[if gte IE 7 ]><div id="panes"><![endif]-->
 <!--[if !IE]>--><div id="panes"><!--<![endif]-->

These codes will load specific line based on users’ browsers as explained in the links. I hate IE.

That dreaded IE6…


Perhaps, web developers worst nightmare is Internet Explorer 6. I usually don’t give a damn to this issue. All troubles while developing site and designing web page, CSS issues, div placement with IE6, I will choose to create a friendlier version for IE6. Forget the those standards and try to make that page appear correctly in IE6. Why? One reason : some users still refuse to change. They would rather spend their time with that ageing IE6.

Bah! But today, after so sick with, real sick with IE6, I have decided to force users to upgrade their IE6 or you are not welcome. It is so hard to create one page that is friendly with IE6 but looks horrible with other browsers. NO! NO! NO! NO!. That’s not gonna happen today.

I have put a code to ask users to upgrade their Internet Explorer 6. I wonder, why users are still tagged with that stupid browser. What a nonsense! I mean, how on earth IE6, the world’s most Worst Tech Products still being used by the general public? Don’t the users know how bad is IE6.

  • As of January 10, 2009, Secunia reports 142 vulnerabilities in Internet Explorer 6
  • Security advisory site Secunia counted 20 unpatched security flaws for Internet Explorer 6, many more and older than for any other browser
  • IE6 does not fully support CSS version 2, unlike most browsers which in turn means web developers must use “hacks” or workarounds so IE6 will display web pages correctly.
  • Internet Explorer 6 is evil – pure and simple.