justira ([personal profile] justira) wrote2006-07-24 02:57 pm

I can't get the fucking trees… Damn! I will kill everyone in the world!

Replace "trees" with "Internet Explorer" and you got it about right.

Those of you who don't get the reference are lame, by the way.

Regardless! I am soon to explode with wrath at Microsoft. See, I program for a living. Currently this invloves less programming and more web design, but I still work with languages and getting programs to cooperate. Currently, I am trying to get a piece of JavaScript/DOM Scripting to work in IE.

See, the funny thing is, I wouldn't need to be tearing my hair out about this shit if IE were a goddamn proper browser in the first place. It has one thing going for it: its extremely forgiving nature in the way of whether you can write HTML correctly (goddammit it's not even that hard) made it possible for millions more people to make webpages.

The thing is, those webpages don't work in any other browsers. You know. The ones who PROCESS THE GODDAMN CODE CORRECTLY.

But IE is the most popular browser, right? So what if the way it processes web languages isn't the way that the W3C recommends and all other browsers adhere to? Majority rules, right?

Well, okay, that train of thought is going in the same direction as this article, which advocates phonetic spelling. The thing is, everyone spells differently. So what if the majority of Americans can't spell the language they speak? We need standards, or else that nice thing we call SHARED LITERACY will go away rather quickly.

Same thing here. It was nice of IE to help the Internet boom along and all, but now it has to deal with the fact that if it parsed code in a sane manner, all those websites it fostered would break =D

For responsible web developers, this means that we usually need to give our "special" browser friend a hand.

In this case, IE is being a complete ass. I had to invent a medium-length Javascript workaround for something that in Safari or Firefox can be accomplished with one line of css:

li:hover {display: block;}

There. Done.

However, I have been trying to get IE to accomplish the same result for the past... four? four or five hours.

The usual solution in these cases is to Java/DOM script a class with an onMouseOver event onto whatever needs hovering. Yeah, sure, that works. The problem is getting it to do it on an item nested in another item that's receiving the same treatment.

Screw you, IE. I'm just trying to get the goddamn dropdown menus to work. First tier works just fine, BECUASE I'M GOOD LIKE THAT, but the second tier just WON'T catch.


I have an unordered list, which is the first tier of the menu. Inside is another unordered list, attached to one of the items in the first list, which is the second tier. It's like, say, going to the View >> Toolbars menu. View is the first tier, Toolbars the second. This workd JUST FINE in Firefox and Safari, but nooooo. IE has to be difficult.

The Javascript currently tacks on an "over" class when you hover over something and takes it away when the mouse leaves the object. That's pretty standards, that works great. The problem comes when I need to tack on a class to something that's being hoevered over that is a child/descendant of something that had to be hoevered over beforehand and already got a class tacked on. You little bitch.

Ugh. I think I have an idea, but still. This is just too goddamn annoying.

Anyway. IE makes my life difficult. Again.





I'm going home and drawing some gay porn now. Take THAT, Bill Gates!

Post a comment in response:

Anonymous( )Anonymous This account has disabled anonymous posting.
OpenID( )OpenID You can comment on this post while signed in with an account from many other sites, once you have confirmed your email address. Sign in using OpenID.
Account name:
If you don't have an account you can create one now.
HTML doesn't work in the subject.


Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.