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