Comment 5 for bug 66726

Thanks, I can confirm that this is fixed now.