Okay, thanks. I reported this one too in our bugtracking system.