Thanks, I was able to reproduce this. This has been fixed for the next version.