bug 122 - in IE an HTTP 204 status may magically become a 1223 status

Issue: #122
Affects: IE6, IE7, IE8?

If you send an XMLHttpRequest that only returns headers (e.g. no content), and you are looking for a 200 status, you'll end up getting a 204 status. In itself that's just fine, but in IE that status might become a 1223 status instead!

Known Workarounds: None. Adjust your response tests as needed to handle this additional IE status.

Related Issues: None.

Bug/Site Feedback |
Submit a bug

bug 326 - field names in IE that break with Mootools

Issue: #326
Affects: IE6, IE7, IE8 Beta 1?
JS Library: Mootools
Mootools Trac#:798

The following fields (name or id) will cause issues in Mootools:

"addEvent", "match", "position", "search"

Due to conflicts when the name exists in Element.Prototype, it will cause issues.

Example:
These will fail when you try to iterate using .each (for example) over a form element array.

<input id="addEvent"/>
<input id="match"/>
<input id="position"/>
<input id="search"/>

<input name="addEvent"/>
<input name="match"/>
<input name="position"/>
<input name="search"/>

Known Workarounds: None. (other than to be careful not to use these field identifiers)

Related Issues: None.

Bug/Site Feedback |
Submit a bug

where are all the IE CSS bugs?

Issue: #450-???
Affects: IE6, IE7, IE8 Beta 1(some)

I received an emai1 {ThisSiteTitleWithNoSpaces@gmail.com} from Nelson T. recently asking where all the IE CSS bugs are? There are several of them, many even have their own name! However it makes much more sense for me to provide a link to better documentation and examples rather than try to re-invent the wheel.

I do have some CSS bugs to report that (I don't believe) are listed elsewhere though, and thus I plan to post those very shortly.

IE CSS Bugs:

The following collection is all available at:
Position Is Everything (PIE), complete with test cases and workarounds (where possible)

• Peekaboo Bug


• Inherited Margins on Form Elements


• Expanding Box Problem


• Quirky Percentages in IE Visual Formatting Model


• IE Line Height Bug


• Border Chaos


• Disapearing List Background Bug


• Guillotine Bug


• Unscrollable Content Bug


• Duplicate Characters Bug


• IE Italics Bug


• Double Float Margin Bug


• Duplicate Indent Bug


• 3 Pixel Text Jog Bug


• Escaping Floats Bug


• Creeping Text Bug


• Missing First Letter Bug


• Phantom Box Bug

Bug/Site Feedback |
Submit a bug

bug 253 - more Array issues in IE

Issue: #253
Affects: IE6, IE7, IE8, IE9 PP4

This is more of a minor issue, but its just one more thing you'll need to watch out for.

Example:

<script type="text/javascript">
  var foo = ['a','b','c','x','y','z',];
  alert(foo.length);
</script>

What would you expect in the alert? 6? Well yes, but not in IE. IE will add a 7th element to the array, which is "undefined".

Think about that for a moment. If the so-called 7th element is "undefined", then why is it there? IE just told us that it is not defined!

Known Workarounds: One. Just be sure that all your Array definitions are "clean" especially if they are generated with some server side code.

Example Workaround Code:

<script type="text/javascript">
  var foo = ['a','b','c','x','y','z'];
  alert(foo.length);
</script>

Related Issues: (bug 230), (bug 181).

Bug/Site Feedback |
Submit a bug