This post originated from an RSS feed registered with Ruby Buzz by Jamis Buck. Original Post: IE is teh 3v1l Feed Title: the buckblogs here Feed URL: http://weblog.jamisbuck.org/blog.cgi/programming/index.rss Feed Description: Jamis Buck's corner of the blogging universe. Mostly about ruby, but includes ramblings on a variety of topics. Latest Ruby Buzz Posts Latest Ruby Buzz Posts by Jamis Buck Latest Posts From the buckblogs here

It’s been said before. I’m sure it will be said again. And again, and again.

IE is teh 3v1l.

You would be hard-pressed to find a browser as worthless in every way as IE. Want to know what happened today?

We were getting reports from users of Backpack that when they tried to print a page from IE 6 they got Javascript errors.

So, thinking it was some bonehead thing on my part I started digging in. I was able to readily duplicate the error on my Windows box, but (lovely IE!) the error message was singularly unhelpful. “Object doesn’t support this property or method”. The location it gave was useless, because it didn’t specify a file—only a line number and character offset. I then installed the MS script debugger, which simply dropped me into the middle of one of the DLL-generated scripts, and told me absolutely nothing about the root cause of the problem.

So, I dropped back to the tried-and-true JS debugging method—start ripping out code until it works, and then add the code back a bit at a time until it breaks again. After about a half-hour of narrowing the search, I found the culprit.

We have a text area named “tags”, which we use to allow users to edit the tags on their pages. Seems like a natural enough name, no?

However, IE didn’t like that name. Oh, it handled it fine most of the time, displaying it, editing it, etc. It handled it fine, right up until the time you tried to print, and then IE choked on it. Perhaps IE uses that name internally during printing or something. Who knows?

Changing the name to “edit_tags” (and fixing all the relevant functional tests and auxiliary scripts that referenced the field as “tags”) caused the error to go away.

Talk about bizarre. If I were Microsoft, I would be frankly embarrassed to own a product like IE.