I think someone ( @User or @User I think? ) from the team noticed this too and is working on a fix. Feel free to send in a bug report though, I don't see one reported already.