You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lorem ipsum dolor sit amet, consectetur adipiscing elit.Proin hendrerit orci in dignissim consequat.Integer ultricies nunc eu massa aliquam tristique.Donec nisl ex, imperdiet ut ultricies eget, volutpat eu nisl.Aliquam varius tincidunt sapien, a pretium mi vulputate sit amet.Sed augue sem, feugiat vel dapibus vel, condimentum a augue.Nam fringilla diam vitae turpis pretium ultricies.Nulla ac ornare dui.Curabitur lacinia felis vitae justo rutrum, et sodales risus congue.Integer posuere felis sed ligula sagittis consectetur.Integer condimentum consequat facilisis.
Ctrl+F, search for varius (or any word that is supposed to be under the find widget).
-> Match is hidden beneath the search widget, although scrolling up reveals it.
I would expect to reveal the match when I hit it, when searching, so that I don't need to scroll back and forth to understand where is the match, if I am a first-time VS Code user.
As a suggestion maybe it is better to do the scrolling the editor up on the user behalf, revealing the search match?
The text was updated successfully, but these errors were encountered:
Consider also the case when user searches for something, then scrolls to the top to reveal the match, then he closes find widget and suddenly decides to search for the same word again. At this point the search widget appears hovering the match and he needs to scroll again up, which is annoying.
Testing #27412:
OS: Windows 10
varius
(or any word that is supposed to be under the find widget).-> Match is hidden beneath the search widget, although scrolling up reveals it.
I would expect to reveal the match when I hit it, when searching, so that I don't need to scroll back and forth to understand where is the match, if I am a first-time VS Code user.
As a suggestion maybe it is better to do the scrolling the editor up on the user behalf, revealing the search match?
The text was updated successfully, but these errors were encountered: