I can't reproduce this with trunk r13527 here.
Can someone else test to see if this is fixed and is indeed a dupe of bug #977003 (per Alex's thought)? Even though this is older, that report is where the fix took place.
I can't reproduce this with trunk r13527 here.
Can someone else test to see if this is fixed and is indeed a dupe of bug #977003 (per Alex's thought)? Even though this is older, that report is where the fix took place.