Search resets current position while new results arrive

[lhecker]

Originally posted by @OAguinagalde here: 32fbb16:

---

On version 1.21.1772.0, whenever using some log reading tool such as logcat or similar, I still get the scroll being triggered on many situations that I wouldn't expect it to:

Situation: logcat or whatever constantly outputs stuff to the terminal. I search for something on the terminal.

• Whenever a new occurrence of my search is output, it automatically jumps to the new one. I'd expect that if I'm on occurrence 10/10, and 2 new occurrences appear, my scrolls would be wherever I originally had it and the active search would stay at 10/12. Instead of that, the active search is automatically set to the latest one (12/12) and it jumps there.
• Also, If I try to "follow" the log output as it is printed to the terminal, as soon as the active search result is out of the screen, it jumps back to it, even if there is no new occurrences of the search, so I'm forced to cancel the search (meaning that I lose the highlighting) to be able to follow the logs being printed.

Is this commit supposed to fix those situations? I'm unsure whether I got my versions wrong or whether these situations where not taken into account when working on it.

---

X3cU8gTVrTpZ5hFR.mp4

[DHowett]

We should fix this at the same time as /dup #17301

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!