Thanks for your bug report. I was able to reproduce this issue. This has been fixed for the next version.