According to the Mozilla bug I added this is indeed a problem in firefox and fixed in the upstream trunk.
According to the Mozilla bug I added this is indeed a problem in firefox and fixed in the upstream trunk.