Hi David Edwards, I just double checked after the latest 5.4.6 release and it would seem that the issue has been resolved. I'm going to mark this closed.