this has been discussed already on some of the code quest tasks, but not resolved yet. It’s not really a papercut, so I am creating a new thread for it.
Currently, the fact that local view has it’s own selection state does way more harm than good. It introduces just obstacles and gives almost no benefit in exchange.
The typical frustrating case is when you want to go to local view with just one object, but you accidentally selected more than one. As soon as you notice it, you select just the one you want, exit the local view and enter it again, but when you exit the local view, it throws away your selection and uses the one before you entered the local view, so you end up repeating the same mistake a few times until you do it right.
I personally can not think of a single useful reason to have different selection for local and non local view, and I challenge anyone to come up with a single reasonable one.