Have you any idea if this has been fixed in Mozilla 1.6?