Based on my test, I reproduced the same problem with you. As mentioned in the comments, this issue has been discussed since 2016, but there is still no good solution.

I recommend that you could report the problem in Developer Community. There are many VS developers who can help here. It is important to note that official staff may only handle this problem when enough people report it.