Skip to content

feat(ui): add scroll indicators to detail view#55

Open
fuleinist wants to merge 1 commit into
Necrom4:masterfrom
fuleinist:feat/scroll-indicators
Open

feat(ui): add scroll indicators to detail view#55
fuleinist wants to merge 1 commit into
Necrom4:masterfrom
fuleinist:feat/scroll-indicators

Conversation

@fuleinist
Copy link
Copy Markdown

Summary

When the detail view (right panel) is scrollable, shows ▲ at top-right when scrolled down and ▼ at bottom-left when not at bottom.

Problem

The detailedResult window is scrollable with Shift+Arrow keys (issue #31), but there is no visual indication that the content is scrollable or what scroll position the user is at.

Solution

Add scroll position indicators:

  • at top-right when scrolled down (not at top)
  • at bottom-left when not at bottom

These only appear when (i.e., when content is actually scrollable).

Use case

Users can immediately see whether the detail view has more content above or below without having to try scrolling.

Testing

  • Built successfully with go build
  • The icons work in both Nerd Font and Unicode fallback modes

When the detail view is scrollable, show ▲ at top-right when scrolled
down and ▼ at bottom-left when not at bottom.

Implements issue Necrom4#31: scroll icon when detailedResult window is scrollable.
@Necrom4
Copy link
Copy Markdown
Owner

Necrom4 commented Apr 16, 2026

Thanks allot for giving a shot at this issue!
To be honest the positioning of these two arrows is not the best.

image

The goal of scrolling was because the window is too small to display the content fully, but in your solution the two arrows placed in the same space as there used to be content, meaning we're removing 2 full lines of information while there's plenty of free space, both to the exterior but also on the border (the arrows could be in the border line, like lazygit does it with it's scrollbar)
image

Also it would be better if the arrows are in the same side, it wasn't intuitive to try and find them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants