Thanks for pointing out this bug! It has been logged in our internal bug system and will be fixed in the final release.