Comment 12 for bug 1720930

Dylan Borg (borgdylan) wrote :

@jsalisbury I can see that this issue remains fixed with 4.13.6 and 4.13.8 (did not test 4.13.7).