Yeah, of course, this is already fixed, will be in the next public build.