Comment # 11 on bug 100726 from
I can confirm this is still a problem (tested 4.15.10).


You are receiving this mail because: