IE7 Supports XMLHttpRequest Natively, My Ass
IE7 Beta 3, installed fresh. Before you ask: yeah, I made sure I had the checkbox checked for "Enable native XMLHTTP Support." So I go to check some of my code and get the following:
A Runtime Error has occurred.Which means a detect script that used to weed out IE6's non-XMLHttpRequest support like this just fucking breaks in IE7:
Do you wish to Debug?
Line: 286
Error: 'XMLHttpRequest.prototype' is null or not an object.
if (window.XMLHttpRequest &&So, basically, this makes me think that they didn't port shit to a native JavaScript object. This just looks like they made an ActiveX control that runs even if you disable ActiveX.
XMLHttpRequest.prototype.isPrototypeOf(someobject)) {
...
} else {
...
}
Labels: ie sucks, internet explorer
posted by The Hater at 10:30 AM
9 Comments:
jab: I just installed some windows updates
jab: and then Windows Update told me I had some security vulnerabilities in my windows software
jab: I click OK and the list of vulnerabilities comes up and one of them says "Internet Explorer is not your default browser
Unfortunately, Microsoft seems to view anything out of its control as a vulnerability...when in fact I generally believe the opposite.
Found the same problem trying to write to a response object which IE 7 doesn't natively support since its a separate control.
Curses IE 7
"Found the same problem trying to write to a response object which IE 7 doesn't natively support since its a separate control."
Any kind of object along these lines exists in IE's "You can't fucking touch me" space. Microsoft basically took JavaScript, ripped out half the purpose of prototyping, destroyed what little performance it had, hit the DOM methods a few times with a blunt object, and called it "JScript" instead.
"Glorious! you've made my day! i am going home... happy fuckin friday"
Why IE Sucks: informative and therapeutic at the same goddamn time.
Keep reading, tell your friends, and send money.
Wow, Mr. anonymous is right! We should just go back to writing basic flat markup and forget all these fancy web apps and interactive flash & javascript bs that everyone is so used to browsing these days. Now, if I can just convince my boss that ajax is worthless, forget about style sheets and javascript, and that we should just code basic monochrome text pages, I'd be off the hook. Unfortunately, he seems to think that our customers who use ajax based web-apps might actually find them to be more useful to their browsing experience & productivity. Of course, not if they use a horses a@@ browser like Internet Explorer, unless I spend half my development time reworking my code to resolve all the stupid problems with this POS.
Way to tell everyone how it should be, Mr. anonymous. Maybe I should come work for you. Btw, does your company even use the web?
Uninteresting, uninformative, rude, and most importantly unhelpful comments on this blog. Won't be comming here for advice anytime soon.
Harold: Why thank you!
I agree with most of the things that where said here. When code I always code against the IE browser cause I know that most of my problems are going to be found here. I think Microsoft should just give up on there pathetic excuse for a browser and trying to push the intellect of this world to theirs old ass way of doing things. I think it would be best for me to go back to the old days. Notepad here I come and an abundance of pure HTML and that's it.
PS. I found this blog cause I have a prototype error in IE and IE ALONE!!!!
Post a Comment
<< Home