This was fixed, but has since become an issue again (see Bug 1172608). *** This bug has been marked as a duplicate of bug 1172608 ***