This post may be something very common and very known, however not everyone knows these, so this post may be useful to someone.

Here is an entire list for this

• lte = Lower Than Or Equal — lte IE6 means that will be loaded by IE6 and lower versions like IE5.5 / 5 and so on and so forth.
• lt = Lower Than — lt IE6 means that only lower versions of Internet Explorer 6 will read that part of the code such as IE5.5 / IE5 / IE4 and so on and so forth.
• gte = Greater Than Or Equal — gte IE6 means that browsers versions higher than 6 or equal to 6 will load that code, such as IE6 / IE7 / IE8 and so on and so forth.
• gt = Greater than — gt IE6 means that browsers versions higher than 6 will load the code such as IE7 / IE8 and so on and so forth.

The most useful part is the ability to load information that is not read by IE browsers at all, you could do something very nice, for example if you wish to drop IE6 support your stylesheet and JS includes will look like this:

The code above will only load the files for IE7+ and all other browsers. A live example of this situation is my own website, which does not support IE6.

Regards

Did you know that IE6(and only IE6, IE7+ doesnt have this issue) has a weird UL/OL bug ?

If not read on

Lets say you want to make a vertical list of items that are linkedable like this

In all browsers except IE6 the list will look OK, however IE6 has a peculiar thing, because you press ENTER and you put the list items each on a new row, somehow IE6 interprets that space as a white line, and you will end up with THIS

THE HORROR!!!!…

Well there are multiple ways to fix this issue, from involving Huge javascript codes to doing some very basic things, and the most basic method of it all is to write those links as follow:

The “wonders” of IE6 …

If you have questions, post them in the comments and i will answer as soon as possible

As you well know Internet Explorer 6 and lower doesnt recognize position:fixed in CSS, in order to get around that issue we need to do this. Btw everything goes in the same css file, the * html star is a hack for IE6 so only it seems the code so other browsers arent affected.

Please note that this means that future absoltute positioned elements will probably break so a safer bet is either to use javascript or just plain use position fixed and suck it up, IE6 is going to die pretty soon anyways

Questions in Comments

Everyone loved valign=”middle” on tables… well life just got better with jQuery. This plugin works flawlessly however make sure that both the element itself and the parent element do not have any top/bottom paddings, else please modify it using the .outerHeight() property that takes into consideration the padding/border of those elements. Tweak and use as necessary.

the JQuery

You can get the benefits of valign=middle no problem.

So just put the jQuery framework script then this script above and call the elements you want to be valigned=middle by using this

Also another VERY NIFTY thing to do is, in order to prevent the user from seeing the javascript process (since first HTML is loaded, then CSS file is loaded, then any images are loaded, then JS is processed) you can do this.

First you need an .outerBox that encompasses the Box element, and then you need to have the box element with a declared height, like #box { height: 300px;}. This workaround is only good for IE 6 since that sucks donkey balls, and has a JS rendering engine from 1000AD. however depending on the amount of content being displayed (like entire columns) IE7 which appeared in 2000AD may require this fix also. Other browsers are OK so this is BS

CSS:

Javascript:

End of story.

And for the other more compatible browsers you can put this in another JS file. The previous one was inserted in the HTML using conditional comments <!--[if IE lte 7]> <script src="./../js/biteMe.js" type="text/javascript"/><![endif]-->

$("#box").vAlign(); and just use Conditional comments to put the IE specific things in so they wont see them, and since you are linking 2 different JS files, (again with conditional comments) you script WONT JAM.

Complex solution for an ancient problem.

Cheers