In my google search for why inline javascript is evil, I was able to come across some interesting information that was relevant and some that was not so relevant. The relevant part was this article on Separating Behavior and Structure. The article was written by the author of, which happens to be a site I often frequent to find out why IE6 is so evil to me. The short answer is usually that there was a bug that I didn’t know about, but the author explains nicely, or has a reference to the explanation and off I go to solve the problem. Definitely a site for the tool box!

The article went into javascript leaking memory at one point, and I had to digress to figure out what that was all about. At work, I use a lot of Spry and YUI, and frankly don’t want to kill people’s browsers because I did something stupid, or didn’t clean up after myself. These two articles go into how DHTML leaks like a seive and how the IE6 bug fix to correct memory leaks was greatly exaggerated. In short, if you tie the DOM to javascript, untie it before you leave. This is something that I am no generally doing today, and must fix in my code, preferably on the library side. I would have thought the libraries would be set up to handle this automatically, but it appears not so much from what I’ve read so far.

The irrelevant information found, while on, also happens to help me with other subjects that I’ve been reading up on and working with. There was an article showing the new CSS compatibility changes, adding the Google Chrome browser to the mix, as well as an article on iPhone events. The iPhone events article was information I have pretty much figured out by having an iPhone myself, but it is a good read anyway just to solidify my findings, or bring to mind things that I may not have been paying much attention to. Through QA, we have found that the Google Chrome browser acts just like the Safari browser, which we were already watching out for. This is good news to me, one less browser that I really have to *worry* about.

I will continue to link back to articles that solve my probems, or at least give relevant details both for my and your reading and educating pleasure.