Yeah, I have this fixed in the most recent build... I'll probably port that fix back into the next public build as well. Sorry about that!
