>>568
That was a bug. I think it is fixed now. Can you confirm?