Comment # 2 on bug 989371 from
The same issue seems to be present in 42.2


You are receiving this mail because: