Comment # 2 on bug 1127584 from
This seems to have been fixed in Build 425.1.


You are receiving this mail because: