This is not a firefox issue but an XULrunner issue, most likely this fix will only land in 1.9 branch
This is not a firefox issue but an XULrunner issue, most likely this fix will only land in 1.9 branch