Unfortunately, this is indeed the current behavior of this button. I just shared your feedback with the team.