Looks like this problem will be fixed on Firefox 3.6.4.