This is a bug and not intended. We're working on fixing it now, and restoring the original intended behavior.