@geekymom
17 years, 2 months ago
So it turns out–this is a Firefox 3 bug! It works on IE, Safari, and Firefox 2.