You're right, I was easily able to reproduce this. I've added it to the to-do list and it will be fixed for the new version 2.0 preview-1a.
