I have reproduced this here, we will investigate further and fix the issue for the minor update following 6.0.0.0.