Dave Woods - Freelance Web Designer UK
Personal Website of a Freelance Web Designer UK
Subscribe in a reader
Categories
Twitter Updates
- RT @eightyonedesign: Blogging tips from the experts - http://tinyurl.com/csnlye 2009-04-24
- RT @sitepointdotcom: 30 Sites For Fantastic, Free Fonts http://tr.im/jzJF 2009-04-24
- @alwyndebruijn Thanks, the redesign has been long overdue :) in reply to alwyndebruijn 2009-04-24
- More updates...
IE6 - CSS Bugs and Fixes Explained
Published by Dave | Filed under CSS, Hints and Tips, Web Design, Browsers, HTML
I hear about designers and developers pulling their hair out all the time saying that Internet Explorer 6 doesn’t do what they expect or that it’s adding hours to development time but is it really the huge problem that everyone makes it out to be or does it just need a little more understanding?
In this article, I’ll hopefully cover the main problems that developers experience with Internet Explorer 6 and explain the solutions for these bugs.
Internet Explorer 6 isn’t perfect, far from it, but unfortunately while the user base for the outdated browser is still high, it’s in our best interest as designers and website owners to ensure that our sites work correctly for the majority if not all of our users.
There are bugs and problems with Internet Explorer 6 (and even IE7) but you may be surprised to hear that for myself, ensuring a website is compatible with IE6 adds next to nothing to development time.
How is this possible? I’ve got experience within the industry and have come across numerous problems, pulled my hair out for hours trying to make IE6 behave the same as other browsers and thankfully, am now in a position that when common problems repeat themselves and patterns emerge, it’s immediately recognizable as to what the problem is and how to solve it.
However, there are a few steps you should always use before you even tackle the problems of IE6.
Code using web standards
The first step is to ensure you have valid code. Create your website using semantic markup which validates and works in the modern browsers. Make sure you have a full, valid doctype and you should be able to create any design which works in Opera, Safari, Firefox and even IE7 with minimum problems and without using any hacks.
Once you’ve ensured that the foundations are in place, you can tackle any issue that IE6 has. Personally, I fix any issues as I encounter them as it’s easier to see which bug I’m dealing with and is easier to put a fix in as soon as it’s uncovered so I would suggest the same approach, especially for any beginner.
Below, is a list of the bugs that I find crop up most often and are the ones I not only find in my work but also are the causes of most problems for users posting on message boards and forums.
Double Margin Bug
The double margin bug in IE6 occurs when a floated element has a margin on the same side as the float.
For example, both of these examples will cause the margin to be doubled in IE6.
#navigation {
float: left;
width: 200px;
margin-left: 10px;
}
#content {
float: right;
width: 500px;
margin-right: 10px;
}
This will render as specified in IE7, Firefox, Opera and Safari but a bug in IE6 will cause the margin’s to render at double the size specified.
It can be particular problematic when dealing with pixel perfect layouts. For example, in the code above the two columns would sit nicely side by side in a 720px container for the modern browsers. However, in IE6 because the margin’s would be doubled, the content column would actually drop now that not enough space is available.
Double Margin Bug Fix
The fix for this is remarkably simple and doesn’t really make much sense, other than the fact that it works.
By applying display: inline; to the end of each style, it remarkably fixes the problem and causes no other side effects in any other browser.
#navigation {
float: left;
width: 200px;
margin-left: 10px;
display: inline;
}
#content {
float: right;
width: 500px;
margin-right: 10px;
display: inline;
}
I tend to find that this little bug causes the majority of layout issues but it’s amazingly simple to fix.
HasLayout
A definition of hasLayout can be found at satzansatz.de and explains it better than I ever could.
Layout is an IE/Win proprietary concept that determines how elements draw and bound their content, interact with and relate to other elements, and react on and transmit application/user events.
This quality can be irreversibly triggered by some CSS properties. Some HTML elements have “layout” by default.
Microsoft developers decided that elements should be able to acquire a “property” (in an object-oriented programming sense) they referred to as hasLayout, which is set to true when this rendering concept takes effect.
This can cause some strange effects with some elements and the particular problem that I usually encounter is when dealing with float clearing but it can also cause problems with boxes treating properties incorrectly as well as various margin issues.
I’ll focus on the main issue that I experience with hasLayout but it’s worth considering that a problem you’re experiencing may be due to this also.
HasLayout Example
I’d use the following CSS for a very simple container that holds navigation and content columns.
#container {
background-color: #CCC;
overflow: hidden;
}
#navigation {
float: left;
width: 200px;
margin-left: 10px;
display: inline;
}
#content {
float: right;
width: 500px;
margin-right: 10px;
display: inline;
}
Using overflow: hidden; on the container clears the float’s in the modern browsers and also applies “Layout” to IE7. However, overflow doesn’t apply “Layout” for IE6 so we need to use another value.
Using a position, float, width, height or zoom will apply layout but some can create undesired effects in modern browsers so what’s the easiest and best fix?
HasLayout Fix
I tend to find that the best method is to apply a width or height. Quite often, you won’t actually want to apply a width or height so the best way of applying this is to use the star hack to apply a small height to IE6 and below only.
This has the advantage that IE6 treats any height as a min-height and will therefore resize itself accordingly anyway.
Therefore, if you add a 1% height, this will correct the HasLayout issue.
#container {
background-color: #CCC;
overflow: hidden;
}
* html #container {
height: 1%;
}
#navigation {
float: left;
width: 200px;
margin-left: 10px;
display: inline;
}
#content {
float: right;
width: 500px;
margin-right: 10px;
display: inline;
}
Using this method will fix most HasLayout issues so is something worth considering if you’re unsure as to why IE6 is displaying the way it is.
Small Height Bug
I’m not sure what the real name is for this bug but I used to encounter it quite frequently within my designs and it occurs when a small height is specified but IE6 seems to completely ignore the height.
For example, the following will render correctly in all the modern browsers but for some reason, IE6 treats the height differently and refuses to collapse down to the 2px height specified.
#corner {
width: 10px;
height: 2px;
background-color: #C00;
}
Small Height Bug Fix
The problem seems to be caused by IE6’s unwillingness to collapse to a smaller height than the base font-size. It therefore will always by default render at a size that allows text to fit into the height available and it’s this that is stopping the height from collapsing.
So to fix this, all we need to do is set a font-size: 0; within the rule.
#corner {
width: 10px;
height: 2px;
background-color: #C00;
font-size: 0;
}
I’ve recently also discovered another solution which should have exactly the same effect. Because the box is stretching to allow for content overflow, we can also specify overflow: hidden; which will cause the box to honor the 2px height and also collapse.
#corner {
width: 10px;
height: 2px;
background-color: #C00;
overflow: hidden;
}
Both of these solutions will fix the issue even as far back as IE5.01 and won’t cause any problems in the modern browsers.
Summary
By no means is this an extensive list of IE6’s browser bugs but in my experience, these are the most common that account for 99% of all browser rendering issues so if you can get a good understanding of these issues and remember their fixes, hopefully your development time should start to drop for the troublesome browser.
Please feel free to comment though if you have any experiences of other bugs or have a browser bug that you’re unsure how to identify.
January 16th, 2008 at 4:12 pm
Thanks for the article Dave, I know I’ll use it as a reference as most the other sites out there make the IE6 bugs more confusing.
January 16th, 2008 at 4:40 pm
Glad you find it useful. It’s a difficult subject to write about really as it’s quite a technical topic but I also like to keep my posts as simple as possible so that beginners can understand them as well so hopefully this article has achieved that.
January 16th, 2008 at 11:01 pm
I agree; the complaints of having to waste hours on ensuring compatibility with IE6 are exaggerated.
I wrote Five simple steps to alleviate IE6 frustration on this subject, which takes a similar tack to yours but is less technical.
January 17th, 2008 at 12:15 am
Hi Peter, thanks for posting that link. I agree with it all apart from the last point.
I do use conditional comments when I need to support IE5.5 and below as supplying different widths for the box model makes sense doing it this way. However, I don’t see any advantages in applying the hasLayout fixes within conditional comments as apposed to the star selector hack?
IE6 wrongly implemented this and in future, no browser will render this the same as IE6 did so it is perfectly safe to use.
On the other hand, I have seen people taking advantage of Safari or Opera’s support for CSS3 selectors and applying hacks to these browsers which is obviously the wrong way to go due to the fact that once Firefox or IE8 support this selector, then they’ll find that their site breaks and will be back to square one.
But using old wrongly implemented hacks like the star selector hack shouldn’t pose any problems whatsover in my opinion and I’d suggest it’s more a personal preference rather than one method being correct over the other.
January 17th, 2008 at 12:47 am
Mmm I really hate that HasLayout bug…
I came across it in an earlier incident and tried to document it but this article seems to explain it better.
I enjoy your writing style. Thanks, good for future reference
January 17th, 2008 at 9:19 am
I like to put all my IE fixes in a separate stylesheet so that my original CSS stays clean and easy to read. Plus, IE takes the extra slight performance hit of calling an extra stylesheet.
January 17th, 2008 at 9:49 am
@Jermayn - Thanks, I’ve never really excelled at writing so just try and put it across as if I was explaining it to someone face to face, hopefully that works.
@Peter - I had this discussion with someone on Sitepoint and we ended up deciding that the performance would be minimal depending on the amount of hacks. Obviously the few extra lines of code in a stylesheet would only affect IE but the consideration that the actually conditional comment would be using space within every page of the site would also effect performance, albeit slightly.
For complex pages that are going to require lots of hacks then I completely agree as it does keep them separate but for simple sites that only need a few hacks then I tend to go for the star selector.
January 17th, 2008 at 5:20 pm
nice post dude.
Can i translate to portuguese and post on my blog ?
Thankz anyway
January 17th, 2008 at 5:25 pm
Hey Dave!
This is a great article - thanks for writing it! It’s clear, and it explains how to fix a few of the painful IE6 issues out there.
Are you planning on writing any more, in relation to any of the other IE6 issues(like min-height/min-width not being supported)?
Cheers,
Luke
January 17th, 2008 at 5:32 pm
@Julio - Yes that will be fine, although a link to this article would also be appreciated.
@Luke - I wrote an article earlier in the week for a layout which implements min and max width which you might find useful and uses expressions to get around IE6’s problems.
http://www.dave-woods.co.uk/?p=140
In terms of min-height. I wouldn’t usually consider that to be a huge issue as IE treats height as min-height anyway so the following lines would treat all browsers the same
#container {
min-height: 100px;
}
* html #container {
height: 100px;
}
In most cases though, I leave height as auto and just let the content control the height but the above solution will work if you do need to use it.
Hope that helps?
January 17th, 2008 at 6:24 pm
1) Use conditional comments, not ‘* html ‘ to fix bugs. Its harder to organise, and doesn’t work with IE 7.
2) Use zoom: 1; to apply hasLayout in IE 6/7, since it has no visual value, (saying zoom to 100%) so is far safer to use.
January 17th, 2008 at 7:43 pm
Great post, can I translate this in spanish to use in my Blog?.
Thanks dude!
January 17th, 2008 at 7:56 pm
@Ben, Thanks for your comments.
1 - In most cases you shouldn’t need to apply the hack to IE7 anyway so that shouldn’t be an issue. For a few small fixes, I don’t see any harm in placing the star hack immediately after the initial code and can actually be easier to organise and maintain. As I mentioned earlier though, it’s really down to personal preference.
2 - Whilst zoom works for applying “Layout” it is also invalid and therefore your CSS won’t validate. Using height: 1%; for IE6 is perfectly safe to use as IE treats this value as a minimum so as long as it’s served to IE6 and below only, then there will be no issues.
@Reymond - Sure, a link back to here would be greatly appreciated though
January 17th, 2008 at 11:51 pm
[…] January 18, 2008 Dave Woods - HTML, CSS, Web Design » IE6 - CSS Bugs and Fixes Explained […]
January 18th, 2008 at 12:24 am
display: inline; also fixes problems with horizontal lists, from my experience.
Drove me crazy!
January 18th, 2008 at 2:25 am
Hey this is great, I would really recommend turning this into a full blown guide, let this be the first draft of sorts and publish examples that we can see (with screenshots et all) I don’t get what you mean by HasLayout Fix however i guess i shouldn’t be hacking CSS to work with Ie 6 at half one in the morning! heh
January 18th, 2008 at 9:31 am
A simple message: THANKYOU (for the the fix to the “Small Height Bug”)
January 18th, 2008 at 4:53 pm
[…] Read the rest of this great article at Dave Wood’s site This entry was written by Robin Wood and posted on January 18, 2008 at 9:53 am and filed under CSS Resources. Bookmark the permalink. Follow any comments here with the RSS feed for this post. Trackbacks are closed, but you can post a comment. […]
January 19th, 2008 at 12:22 am
[…] Dave Woods - HTML, CSS, Web Design » IE6 - CSS Bugs and Fixes Explained (tags: css ie webdesign hacks ie6 hack) […]
January 19th, 2008 at 12:23 am
[…] Dave Woods - HTML, CSS, Web Design » IE6 - CSS Bugs and Fixes Explained (tags: css ie hacks web) […]
January 19th, 2008 at 1:30 am
[…] Dave Woods - HTML, CSS, Web Design » IE6 - CSS Bugs and Fixes Explained - In this article, I?ll hopefully cover the main problems that developers experience with Internet Explorer 6 and explain the solutions for these bugs. […]
January 20th, 2008 at 4:20 pm
[…] IE6 - CSS Bugs and Fixes Explained Another nice reference post. Dave Woods looks at a rogues gallery of cross-browser rendering issues. […]
January 21st, 2008 at 1:43 pm
Hi! Dave.
Thanks for the comment.
There are helpful also to the Japanese person.
January 23rd, 2008 at 1:16 am
Hi Dave, thanks so much for the Double Margin Bug Fix
January 29th, 2008 at 6:50 am
Hi Dave!
I had given up on getting my personal site working in IE6 until I found this trying to get another site to work. A couple of display:inline and one font-size:0 later, it looks 99% like it’s supposed to instead of the 5% before!
Thanks so much for these tidbits!
January 29th, 2008 at 2:40 pm
Thanks for a great post, Dave!
Your tips saved me a lot time, especially the HasLayout fix.
Good luck.
January 29th, 2008 at 4:13 pm
… as well as “Small Height Bug”!
January 30th, 2008 at 4:43 am
I appreciate the post Dave, but I have to disagree. CSS is only a minor part of what is wrong with IE6 (and IE7)
The DOM, and JavaScript for IE is severely broken.
Of note, here are 30+ bugs in IE that will drive any developer up the wall,
http://webbugtrack.blogspot.com/search/label/DOM%20Methods
and they include everyday things like calling .getElementById(), or setAttribute()
January 30th, 2008 at 9:44 am
Hi Max, Thanks for your comments.
My specialist area is design, HTML and CSS so unfortunately I’m only really able to comment on this area and getting the look and feel of a site right which is a big enough topic to cover on its own anyway.
Thanks for the link as well though as it may prove useful to others who deal with JavaScript and lets hope that IE8 has corrected most of those bugs (although I suspect it will have introduced some new ones).
January 31st, 2008 at 5:53 pm
Hi Dave, thanks for the Double Margin Bug Fix writeup this has solved all of my CSS issues…
… Where do I pay
February 2nd, 2008 at 9:42 pm
Great post. Appreciate the fixes for the IE bugs. It seems like every site I do, I run into the usual bugs. I did find a cool Dreamweaver extension for creating valid CSS layouts VERY easily. Check it out at WebAssist: http://www.webassist.com/professional/products/productdetails.asp?PID=135&WAAID=649
February 14th, 2008 at 9:41 pm
Thanks for a highly useful post! I just encountered a new IE bug (new to me, at least, and I’ve been coding CSS since 2000). I also provide the fix.
When using CSS to provide a “you are here” highlight in a menu, nesting order makes the difference in formatting. It doesn’t matter if it’s nested correctly. IE likes things nested in a particular order. The break is that when you are on the highlighted page, IE adds a line, as if you had inserted a ‘br’ tag. Here’s what I encountered:
- I used ‘class=”name”‘ inside the ‘a href’ tag to identify the page for the highlight CSS
- I used ’strong’ tags to boldface my menu items
- If the ’strong’ tags were nested outside the ‘a href’ tags, IE inserted an extra line beneath the item, but only when on the page matching the class name.
- If the ’strong’ tags were nested inside the ‘a href’ tags, then all was well.
Just another weirdness in IE that I thought I’d share with the class
February 15th, 2008 at 9:34 am
Hi Alex,
That sounds like it was probably a haslayout issue but I’d need to see the code or a link to be able to provide a solution.
I suspect that providing display: block and a width (or other methods discussed in the article above) to both the strong and a tags would have solved this.
I know, you shouldn’t have to but that’s IE for you
February 23rd, 2008 at 9:17 pm
I’ve been tearing my hair out all afternoon wondering what was going wrong on a site I’m developing. After scouring the internet trying to find out, I found your information on the Double Margin bug. Many thanks for the fix. I can sleep well tonight!
March 12th, 2008 at 12:38 pm
[…] are you going to need to put in your ie.css file? There are entire sites dedicated to Internet Explorer 6 bugs and workarounds; no point in rehashing them all here. Two that you’re sure to run into […]
March 13th, 2008 at 2:28 am
Hi Dave,
The small height bug can be fixed by changing the font-size or overflow, but for some reason this doesn’t seem to work when applying the style via javascript (element.style.fontSize = ‘0px’). I haven’t found a workaround for this yet. Weird, huh?
Parker
March 13th, 2008 at 2:34 am
Whoops, disregard my previous post. I had left a console.log in my code call that was silently failing.
March 27th, 2008 at 11:59 am
IE stinks. Every web developer should do everything possible to get Firefox widely used and this piece of garbage consigned to history where it belongs.
March 27th, 2008 at 12:45 pm
Hi Jim, yes IE stinks but if you understand why it does then it isn’t all that difficult to correct any bugs.
April 4th, 2008 at 3:54 pm
brilliant article you have helped me and my collegues a great deal - espically with the double margin trick.
I ran into a problem today I was using a image float in a div tag - but the float would not work correctly. this was because the text (p) had a width set to it - firefox displayed it correctly but good old ie7 could not understand a image float with a width set on the text.
April 11th, 2008 at 1:58 pm
Hey guys,
I tried out the above double-margin fix, but my website - currently online at healthspaguru.com is still getting that IE6 bug - can anyone shed some light?
Thanks in advance.
April 20th, 2008 at 3:47 am
[…] are you going to need to put in your ie.css file? There are entire sites dedicated to Internet Explorer 6 bugs and workarounds; no point in rehashing them all here. Two that you’re sure to run into are […]
May 13th, 2008 at 8:13 am
Hello! I have a problem in IE with layout. It is different from the layout in Mozzila. I cant fix the problem.Greetings!!!
May 14th, 2008 at 9:49 pm
Hi Dave, just wanted to thank you for two of the bug fixes here that saved me a lot of time and aggravation! I doubt I would have been able to figure it out on my own.
May 15th, 2008 at 9:43 am
Great all round list of bugs. Very useful thanks.
I found another bug thats not listed that caused me some problems called IE6 Multi Class Bug.
heres some info on it:
http://sonspring.com/index.php?id=102
I hope this helps people
June 11th, 2008 at 5:53 pm
Thank you so much for this article. Very useful!
June 15th, 2008 at 7:35 am
Brilliant.. thank you very much for the HasLayout hack. I never would have known that was the problem with my site. And even if I had known, I would never have thought of that 1% fix. Thanks once again.
June 26th, 2008 at 12:37 pm
Thanks for saving my day with such a well explained article!! Knowing such an easy solution to the double-margin bug has saved me hours of time - I Have seen many articles on float drops etc that totally neglect to identify this bug as the MOST likely cause……
June 30th, 2008 at 9:37 pm
Dave, a lot of thansk for you! Greate article (abd especially Double Margin Bug Fix!)
July 17th, 2008 at 1:02 am
Great article. It was very helpful!
August 14th, 2008 at 2:05 pm
hi dev
Thx alot 4 this usefull artical .
August 29th, 2008 at 11:51 am
great explanation and fix. I’d been struggling for a day trying to work out why IE6 was having issues - after reading the article it took 5 min to fix.
September 8th, 2008 at 10:12 am
Thank you very much!!!. It’s the best thing I ever found on earth. It helps me reduce more than 5 hrs fixing IE6 bugs and some unsolvable bugs.
September 19th, 2008 at 4:02 pm
[…] Dave Woods IE6, tricks […]
October 7th, 2008 at 11:40 am
[…] the solution is out there - and its not even a hack! I ran into the article <a href = “
October 14th, 2008 at 6:08 pm
[…] Fix the Big Problems: fix the big IE6 issues
October 16th, 2008 at 9:37 pm
Thanks a lot for this article. I’ve come across most of these bugs before except the height issue (which just happened to be the issue I was having when I read this article) Thanks again.
December 2nd, 2008 at 5:47 am
It seems like you know what you’re talking about based on this article and the “HTML and CSS expert” title you give yourself – but why, then, are you using a free CSS template… Did you design it or did you pick it up from the link in the footer?
December 2nd, 2008 at 5:59 pm
Hi Chris,
It is a free template but am currently in the process of create my own theme which should be live for the new year.
I initially used this template as a stop gap so that I could write some articles while I was working fulltime and doing some freelance work but will have my own theme online shortly
Cheers for the comments.
February 27th, 2009 at 9:53 am
[…] IE6 - CSS Bugs and Fixes Explained […]
March 4th, 2009 at 9:40 pm
[…] IE6 CSS Bugs and Fixes Explained […]
March 5th, 2009 at 8:45 pm
Hello Dave,
I do skins for invision and zetaboards. I don’t have a problem with the I.E. bug got invision, but lately it has been brought to my attention it is causing some grief on zetaboard especially for anyone using I.E. which I don’t. I design all my skins in FF. I read your article, and it sounds simple enough. My problem is I am not sure where in the CSS for zetaboards I am supposed to do this. I tried one fix and that didn’t work. Any help would be greatly appreciated as this is driving me crazy.
Spice
March 6th, 2009 at 11:12 am
nice explanation of the bugs described. Thanks for posting
March 6th, 2009 at 11:46 am
Hi Dave!
Thanks a lot for that! No more _margin with invalid code. The display: inline; works great and validates!!!
March 6th, 2009 at 1:14 pm
Thanks loads Dave,
this article has fixed my IE 6 woes. I am really new to CSS (i am php programmer) and I always thought it would be much harder to fix the bugs with IE6 than this.
Cheers
Ally
March 7th, 2009 at 5:40 pm
thx, the display:inline fixed my prob.
March 15th, 2009 at 10:44 pm
thanks for simplifying this topic. i don’t find IE6’s bugs to be all that troublesome to work around, and you did a fabulous job of explaining a few very important fixes.
about what you said @ comment #13, i like pages to validate as well, but i thought that the *html hack caused pages to invalidate?
here’s my #1 tip, for what it is worth, and i’m sure that it is a “just understood” rule for you and many others:
i write my css for modern browsers first and make sure that everything displays properly there first. then, i go back and write the rules that will force IE5 and 6 to display as close to the modern browsers as possible.
if it’s a small site, i tend to agree with you and just include those rules in the same style sheets as the rest. but on larger sites i include an IE style sheet that loads last. because my css was written for the better, modern browsers it’s easy to go in and just delete the IE style sheet should that day ever come.
also, thank you for addressing this issue in the first place. i’m frankly sick of reading articles about how we, as DESIGNERS, should simply ignore IE 5 and 6. lots of end users in schools and corporations are forced to view websites in those older versions of IE, and designers should make every effort to make sure they have a good user experience.
March 15th, 2009 at 11:57 pm
Hi Patrick, Thanks for the feedback. The * hack is valid, it’s just that it shouldn’t actually make any sense to browsers that make it such an odd one but it’s perfectly valid to use.
I do agree though that for larger websites then it is a good idea to put any fixes in an IE only stylesheet and I have started to use zoom: 1; to apply haslayout fixes for the older versions of IE.
I do also agree with your last point although it does really depend on the site and what visitors are being targeted. For example, I’d have no problems ignoring IE6 users for my own personal website which is aimed at other web designers, however I would always ensure a website worked fine in IE6 for any client website at the moment.
March 16th, 2009 at 12:14 pm
Useful little article, particularly the Small Height bug fix, which I hadn’t seen before.
I’ve seen this in effect in the past, but don’t see it as much these days as you usually only see it when you’re using empty or decorative elements, which I all but avoid now. Thanks for the tips
March 19th, 2009 at 6:04 pm
great!, thank you for posting this saved me a lot of re-work with a site I am working on.
I never understood that float: right; margin-right:0px; error (until now) but just looking at your problem and solved snippet I fixed it.
I’ll remember that for next time
March 28th, 2009 at 6:03 pm
Sorry, I disagree. It doesn’t matter if IE6 adds 5 minutes or 5 hours to development time, the point is that the hacks used to make it comply with standards ought to be unnecessary. If microsoft had followed the web standards that every other browser follows then we wouldn’t even be having this discussion.
March 30th, 2009 at 4:32 pm
Steve, I agree with you and am not happy that even on the day IE8 was released it was still behind all the other browsers in terms of the number of CSS selectors it supports so I’m as unhappy as you are.
However, this article was to illustrate that it isn’t as hard as many developers will have you believe once you understand the problems and that there is no need to pull your hair out for hours if you know about these little fixes.
April 7th, 2009 at 11:34 am
Dave - great article - clear, concise & just what the doctor ordered for a css newbie like me who despiseth of ie6.
April 14th, 2009 at 8:57 pm
Much appreciated, spent a mere 20ish minutes trying to fix an issue but it could have been far longer if I didn’t jump right into google.
April 20th, 2009 at 10:11 am
[…] IE6 Bugs and Fixes […]
May 7th, 2009 at 7:52 am
IE 6 era ends
May 20th, 2009 at 6:28 am
Thank you for the Small Height Bug fix. I looked everywhere for a solution, and would not have thought of it myself. You saved my sanity!
June 17th, 2009 at 4:01 pm
Thanks, this is an excellent article.