Comment 21 for bug 66332

Mozilla seems not to care about this issue per the upstream bug report; nor do I any longer (I don't have the time to learn the Mozilla source code base and I've found software that works for the task). I'm going to mark this as closed in Ubuntu since it'd require upstream to do something about it in the first place; it's somewhat pointless to keep it open.