-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't let results hide under search box #4407
Labels
Area-TerminalControl
Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
Help Wanted
We encourage anyone to jump in on these.
In-PR
This issue has a related PR
Issue-Task
It's a feature request, but it doesn't really need a major design.
Needs-Tag-Fix
Doesn't match tag requirements
Priority-3
A description (P3)
Product-Terminal
The new Windows Terminal.
Milestone
Comments
fredless
added
the
Issue-Feature
Complex enough to require an in depth planning process and actual budgeted, scheduled work.
label
Jan 30, 2020
ghost
added
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Needs-Tag-Fix
Doesn't match tag requirements
labels
Jan 30, 2020
zadjii-msft
added
Area-TerminalControl
Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
Issue-Task
It's a feature request, but it doesn't really need a major design.
Priority-3
A description (P3)
Product-Terminal
The new Windows Terminal.
labels
Jan 30, 2020
zadjii-msft
removed
the
Issue-Feature
Complex enough to require an in depth planning process and actual budgeted, scheduled work.
label
Jan 30, 2020
I think you've got a good point here. |
Yep, this is reasonable. |
DHowett-MSFT
removed
the
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
label
Jan 31, 2020
Moved to v1.0 - we can talk about this in a later scrub. 😄 |
Also tagging this to #3920 since this would be something nice to deliver as a part of an updated Search experience. |
This was referenced Sep 14, 2022
github-project-automation
bot
moved this from Should be written
to Done
in Terminal Walkthroughs
Aug 7, 2024
microsoft-github-policy-service
bot
added
the
Needs-Tag-Fix
Doesn't match tag requirements
label
Aug 7, 2024
DHowett
pushed a commit
that referenced
this issue
Sep 24, 2024
Adds a scroll offset to avoid hiding the current search highlight with the search box. - Offset is based on the number of rows that the search box takes up. (I am not totally sure I am calculating this right) - This won't help when the current highlight is in the first couple rows of the buffer. Fixes: #4407 (cherry picked from commit 0bafab9) Service-Card-Id: PVTI_lADOAF3p4s4AmhmszgTTNTE Service-Version: 1.21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-TerminalControl
Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
Help Wanted
We encourage anyone to jump in on these.
In-PR
This issue has a related PR
Issue-Task
It's a feature request, but it doesn't really need a major design.
Needs-Tag-Fix
Doesn't match tag requirements
Priority-3
A description (P3)
Product-Terminal
The new Windows Terminal.
Description of the new feature/enhancement
Sometimes a search result can hide under the search box, this is confusing to the uninitiated. Search should always show the found item without hiding it under a UI element.
Proposed technical implementation details (optional)
Perhaps scroll the search result further up to pad it away from the search box in most situations - not very elegant though.
The text was updated successfully, but these errors were encountered: