Bugs that have survived the "release to web" (RTW) deadline of Internet Explorer 8 will be considered for the next version of Internet Explorer, according to Microsoft.
All Postponed bugs are now active for consideration in the next version of Internet Explorer. We resolved and closed all other bugs submitted since IE8 Beta 1. The Internet Explorer 8 Feedback website on Microsoft Connect will remain open and we will not delete any of your previously submitted bugs. Right now we are looking for new IE8 bugs and bugs that have regressed (meaning the bug was previously fixed and now occurs in IE8 RTW).
In the next couple of months, we will introduce a new type of feedback form designed specifically to handle improvements for the next version of Internet Explorer. Please stay tuned for more information.
Unfortunately, this leaves a LOT of bugs open, many of which impact on site designers. You can view the outstanding bugs here: https://connect.microsoft.com/IE/Feedback
Some of the known bugs include:
- Rounding bug with em calculations: Only known workaround - don't use ems for line heights and be careful of even using ems for any other sizing.
- @import a stylesheet for print media fails. If you want to include a print media style sheet, don't use @import
- Source View stops on null byte. If you are trying to view a page in Source View and either don't see anything, or only see part of the page, then the chances are your page contains JavaScript and you have hit a null byte bug that Microsoft was informed about over a year ago. The solution - use IE8's Developer Tools or an external editor to view the source code.
- Styled <noscript> shows through even when scripting is present. Paul Gobée put up a demo page on positioniseverything.net to show this in action.
- The align attribute of COL elements is ignored.
- Percentage width floats cause justified text to move (this is a regression - IE7 did not have this problem).
- Text resizing problem. If text is resized using the menu bar (View | Text Size) the characters are resized but the text is not reflowed. This results in lines truncated by their container or not filling its width, and strange effects on line-height. This corrects itself if the user refreshes the page but, to date, the only known workaround is to ensure you do not use fixed-size fonts on your site. Of course, if you use ems, you risk encountering the rounding bug I mentioned earlier!
IE6/IE7 Bugs Still Present in IE8
- DOM nodeType constant values are not enumerable, are not accessible:
Ref: DOM 2 Node IDL http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1950641247 - An unclosed <p> tag immediately preceding a form element or <table> should be implicitly closed by IE when parsing and building DOM tree. It is not.
See the closed bug report here: https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=338580 and test example here: http://www.cs.tut.fi/~jkorpela/test/form.html - Limited stylesheet nesting levels when using
@import- nesting is only 3 levels deep. - An HTML comment inserted after the XML declaration and before the DOCTYPE declaration will trigger Quirks Mode (this was also the behaviour of IE7. In IE6 an XML declaration would trigger Quirks Mode).
More Reading
Coding & Dreaming's IE 8 bugs list by James Hopkins
Internet Explorer 8 bugs by "mvdleij"
Also take a look at Gerard Talbots bug list.
This is not related to bugs, but is important reading nevertheless: Differences between IE8 Compatibility View and IE7
If you find bugs that are affecting your site design, check the IE Bug tracker and if it's not already reported, add your report. While you are there, vote for any outstanding issues to help Microsoft see which ones should take priority. Overall, IE8 is an improvement from earlier versions of Internet Explorer. It's just a shame we now have more cross-browser compatibility issues to deal with.
Have you experienced any rendering issues with your sites? Do you even bother designing for Internet Explorer now?
If you enjoyed this post, make sure you subscribe to my RSS feed!
{ 8 comments… read them below or jump to the comment form to add your thoughts }
IE8 Bugs Site Designers Need to Be Aware Of http://lynnepope.net/ie8-bugs
For reasons that are beyond me, the bug reporting process for IE8 has been restricted to a number of approved testers only (myself included). LIke I mention on my bugs page, if anyone thinks they've come across a bug that isn't already in Connect, and they don't have permissions to submit a report, please get in contact with me and I'll submit a report on their behalf.
@James Hopkins: Thanks James. I don't understand why Microsoft has done this either. Not only are they only taking bug reports/comments/additional info/ratings from only a select group, but they seem to have removed other accounts from Connect. To add to the confusion, they are taking bug reports on the IE8 BETA forum, which is still called "Internet Explorer Beta Feedback", and from the IE Wed Development forum on MSDN. One would think its plain common-sense to have all bug reporting in one place!
"Rounding bug with em calculations: Only known workaround - don't use ems for line heights and be careful of even using ems for any other sizing. "
Not using ems effects site accessibility. The true work around is to supply an IE8 only stylesheet which uses px values. Or just emulateIE7 - ugh.
I started a discussion about this because I can't believe that Microsoft aren't going to fix the problem.
Hopefully MSFT will take note and this issue will get enough traction for Microsoft to bring in a fix soon. I'm not holding my breath though!
I found somthing Im not sure its a bug but its hell of annoying. Kept me awake for several hours. When trying to center a div using css margin: 0 auto. It is very important to have a correct dtd, this is understandable (not sure if its good, but understandable). What is beyond me is why using comments ahead of the doctype declaration would some how impair some of the css functions such as margin: 0 auto; Spread the word! I have seen countless questions on forums on this one and not seen this "solution" been offered anywhere.
@Pablo: Conditional comments should never be before the DOCTYPE declaration. If they are used, they should be used between the
tags. It may be that using invalid code ahead of the DTD is causing IE8 to choke. It's interesting that it's ignoring the auto margin though. This is something that is common in IE6, where people activated Quirks Mode by using an xml prolog before the DOCTYPE, but is not something I have been able to reproduce in IE8.Try moving your conditional comment between the tags and see if this makes a difference.
MS Internet Explorer 8 (IE8) has some bugs.runtimeStyle[] gives me error message "Object doesnt support this property or method" Selami OZLU
{ 1 trackback }
Leave a Comment