Annoying, uncommon bugs

This post is dedicated to those little bugs that only seem to happen to your project, and no one else on the Internet. Luckily, this wasn’t completely the case this time, as I did manage to find some links after modifying my search query numerous times.

First of all, something arbitrary:

Prototype 1.5.0_rc2’s AJAX works in IE, but not Firefox

The Rico Forums supply a patch that fixes this problem that seems to occur when you’re running Rico concurrently with Prototype.

I started rc2 instead of rc0 and suddenly my news headline component refused to fire off any XmlHTTPRequests, and thus failed to retrieve any story summaries from the server. The component still worked in Internet Explorer 6 and 7 though, so I was kind’ve lost. After applying the patch mentioned in the link above, everything returned to normal.

In my case, I wasn’t running Rico with Prototype, but rather moo.fx, along with some other small JS scripts - anyway, one of them broke it.

Internet Explorer: bold text and opacity filter causes corrupted fonts

This took me a while to find - using moo.fx’s fx.Opacity or Prototype’s Effect.Pulsate (make that anything that uses IE’s alpha opacity filter) on bold text causes it to appear corrupted (blurry, over-bolded, distorted) in IE 6.

Again, luckily, I stumbled upon this solution: IE bold text + opacity problem .

Basically, to fix this, you have to ensure you’re setting the background colour for the element that you are fading in/out. In other words, background: #FFF;.