Good catch. I was wondering where was this bug when first heard about it. Hopefully, latest build fixes it.
