Browser bugs: Posts

via ajaxian:

Alex Bosworth has written a lot on practicalities of Ajax including quirks. His latest piece details the Rocky Shoals of Ajax Development in which he discusses:

Browser Quirks and Limitations

• MLHttpRequest can’t access remote server
• Multiple Ajax Requests are not fired in order
• Asynchronous XMLHttpRequests responses will arrive in no particular order
• XMLHttpRequest does not requires the use of XML
• Ajax uses UTF-8
• Ajax requests are url encoded
• XMLHttpRequest cannot transmit files
• Firefox: Synchronous XMLHTTPRequests lock up Firefox
• IE: XMLHTTPRequest Objects are not reused in IE
• IE doesn’t use cached images when Javascript inserts HTML with images
• IE: Closures with circular references in IE cause memory leaks
• IE: Avoiding aggressive caching in IE
• IE corrupts gzipped javascript files
• IE doesn’t cache gzipped Javascript files

Thank you Microsoft!
Microsoft’s lame attachEvent protocol (instead of the standard addEventListener) doesn’t pass along the element that caught the event. So if you use attachEvent to attach something to, say, onclick, and then the user clicks that object, then the function you attached can’t do something like “this.id” because “this” isn’t defined. INSTEAD it’s part of the window.event object (there’s only one). this function returns the right object. Call it like so:
| Read the rest »