This is actually a bug (not by design) and we're investigating a fix for a future update. Hang tight!