Comment 62 for bug 940631

Running 60.5.0 on Windows 10, no longer have this problem