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