If I was in one of those Geek Conventions, and I just announced the title of my presentation, I'd probably be booed. Some will walk away, and some will throw a tomato or an egg at me. But I'm sure some WISE geeks will stick around and listen to me.
We all know that IE has its flaws. And I will not in anyway try to downplay them. I, for sure, know that IE is slow. However, this is prejudiced to only the versions I've used, i.e. up to 8. I don't know the performance and security of >8 IE browsers.
Anyway, back to my post. I recently completed two apps. One for a client, one for myself. They were both tested thoroughly, with Chrome and Firefox. Everything was well, and since I wasn't doing anything that is known to have issues to IE, I figured my code would work.
Lo and behold. My partner went to present the project to a client. The client was using, yes you guessed it, IE. And when he did, something didn't work.... It was a jQuery ajax call. It just didn't work. I really didn't know what the problem was. However, since the ajax call took place via an onChange event of a form, I figured there was something wrong with the way IE handled the onChange event. I went around searching around the internet for solutions, when I realized I was searching for the wrong thing. I had used the onChange event earlier in the same project, and it had worked just fine.
So now, I went in search of a tool that would enable me to debug JavaScript on IE. I found this very useful tool, that I recommend. http://www.debugbar.com/ If you want to debug JS in IE, this is your tool. It saved my behind.
It was only when I used this tool, that I noticed there was a bug in the server side code that prevented my code from working in IE. Well, Chrome and Firefox ignored these, but IE didn't. IE must be saying "Who yo daddy???" lol! When I fixed the bug, it worked fine in IE.
I've also learnt, in my search for the onChange event, that of all browsers (there was no date in the post, so I don't know how recent it is), IE is the only browser that handles the onChange event as it is specified in the Specification.
Is IE the worst browser?
We all know that IE has its flaws. And I will not in anyway try to downplay them. I, for sure, know that IE is slow. However, this is prejudiced to only the versions I've used, i.e. up to 8. I don't know the performance and security of >8 IE browsers.
Anyway, back to my post. I recently completed two apps. One for a client, one for myself. They were both tested thoroughly, with Chrome and Firefox. Everything was well, and since I wasn't doing anything that is known to have issues to IE, I figured my code would work.
Lo and behold. My partner went to present the project to a client. The client was using, yes you guessed it, IE. And when he did, something didn't work.... It was a jQuery ajax call. It just didn't work. I really didn't know what the problem was. However, since the ajax call took place via an onChange event of a form, I figured there was something wrong with the way IE handled the onChange event. I went around searching around the internet for solutions, when I realized I was searching for the wrong thing. I had used the onChange event earlier in the same project, and it had worked just fine.
So now, I went in search of a tool that would enable me to debug JavaScript on IE. I found this very useful tool, that I recommend. http://www.debugbar.com/ If you want to debug JS in IE, this is your tool. It saved my behind.
It was only when I used this tool, that I noticed there was a bug in the server side code that prevented my code from working in IE. Well, Chrome and Firefox ignored these, but IE didn't. IE must be saying "Who yo daddy???" lol! When I fixed the bug, it worked fine in IE.
I've also learnt, in my search for the onChange event, that of all browsers (there was no date in the post, so I don't know how recent it is), IE is the only browser that handles the onChange event as it is specified in the Specification.
Is IE the worst browser?
