It is fixed on the trunk and on the 1.0.x branch (but after the release of 1.0). Bug 112908 comment 70 says it has been fixed on the 1.0.x branch (thus the fix will be in 1.0.1) *** This bug has been marked as a duplicate of 112908 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.