...but if they can't implement half of its uses correctly they shouldn't pretend to support it.
Well, technically I guess they haven't
). Since all of us have to resort to a series of if/then statements just to create one
fucking object in more than one browser.
That doesn't even begin
to talk about the frustration IE creates when you try to use the goddamn thing. For instance:
- I have an XMLHttpRequest I need to make
- It uses a unique token to keep track of which request has just loaded and where the response should go.
- Since it uses XML (and IE fucking chokes on application/xml, but I'll save that for another post), I have the XML responses getting served as text/xml.
- I need to copy the contents of an element (which has an xmlns="http://www.w3.org/1999/xhtml" as it should) into the DOM
that importing nodes using something (say...element.importNode) would work without the browser all but crashing on you. You'd think
that IE would recognize that you have an XHTML DOM in the browser window and an XHTML DOM in the form of element X
In comes yet another fucking if/then for IE.
However...wait for it...IE can't handle its own required call to element.cloneNode
. Because I have a form coming in.
Fine, I'll take the form out and copy form inputs
into the fucking thing. But the most I can get out of the piece of crap: null. Yes, it takes the XML response, recognizes the nodes enough for me to get the token back out of it and then it chokes and dies on the element using the XHTML namespace.
Brilliant.I'll post the work-around later...once I make one.
Labels: ie sucks, internet explorer