Skip to content

re-add scrollbar to command#2530

Merged
Sebastian-ubs merged 2 commits into
mainfrom
re-add-scrollbar-to-command
Jul 17, 2026
Merged

re-add scrollbar to command#2530
Sebastian-ubs merged 2 commits into
mainfrom
re-add-scrollbar-to-command

Conversation

@Sebastian-ubs

@Sebastian-ubs Sebastian-ubs commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

before
image

after
Screenshot 2026-07-09 192959

This change is Reviewable

@Sebastian-ubs

Copy link
Copy Markdown
Contributor Author

The effective change is only removing tw:no-scrollbar

@imnasnainaec imnasnainaec left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imnasnainaec partially reviewed 11 files and all commit messages, and made 1 comment.
Reviewable status: 11 of 12 files reviewed, 1 unresolved discussion (waiting on Sebastian-ubs).


lib/platform-bible-react/src/components/shadcn-ui/command.tsx line 149 at r1 (raw file):
Devin observes

lib/platform-bible-react/src/components/shadcn-ui/command.tsx:R146-149
Scrollbar visibility change affects all CommandList consumers

Removing tw:no-scrollbar from CommandList (command.tsx:149) is a visual change that propagates to every consumer: combo-box.component.tsx, marker-menu.component.tsx, comment-editor.component.tsx, project-selector.component.tsx, recent-searches.component.tsx, book-chapter-control.component.tsx, multi-select-combo-box.component.tsx, select-books-picker.component.tsx, and overlay-command-palette.component.tsx.

Some of these (e.g. compact combo boxes or the command palette) may have been designed with the hidden-scrollbar aesthetic in mind. If any consumer needs the old behavior, it can pass className="tw:no-scrollbar" to override, so this is non-breaking — but worth a visual check across all consumers.

Have you evaluated whether tw:no-scrollbar should be added to any of the consumers that weren't the target of this change?

@imnasnainaec imnasnainaec left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imnasnainaec made 1 comment.
Reviewable status: 11 of 12 files reviewed, 1 unresolved discussion (waiting on Sebastian-ubs).


lib/platform-bible-react/src/components/shadcn-ui/command.tsx line 149 at r1 (raw file):

Previously, imnasnainaec (D. Ror.) wrote…

Devin observes

lib/platform-bible-react/src/components/shadcn-ui/command.tsx:R146-149
Scrollbar visibility change affects all CommandList consumers

Removing tw:no-scrollbar from CommandList (command.tsx:149) is a visual change that propagates to every consumer: combo-box.component.tsx, marker-menu.component.tsx, comment-editor.component.tsx, project-selector.component.tsx, recent-searches.component.tsx, book-chapter-control.component.tsx, multi-select-combo-box.component.tsx, select-books-picker.component.tsx, and overlay-command-palette.component.tsx.

Some of these (e.g. compact combo boxes or the command palette) may have been designed with the hidden-scrollbar aesthetic in mind. If any consumer needs the old behavior, it can pass className="tw:no-scrollbar" to override, so this is non-breaking — but worth a visual check across all consumers.

Have you evaluated whether tw:no-scrollbar should be added to any of the consumers that weren't the target of this change?

When pushed, Devin is only concerned about the command palette and recommends a side-by-side visual comparison.

@Sebastian-ubs

Copy link
Copy Markdown
Contributor Author

Yes, the intention is to push it to all of them

@imnasnainaec imnasnainaec left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imnasnainaec reviewed 1 file and resolved 1 discussion.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved.

@merchako

merchako commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Concern: on macOS, it's normal for the app to not add scrollbars because our native environment adds them in ways that respect OS settings. There's an (unconfirmed) risk that this change might override that behavior, @Sebastian-ubs

@merchako

Copy link
Copy Markdown
Contributor

Also, change height to be an amount that's not divisible by the row height—that will default the Illusion of completeness

@Sebastian-ubs

Sebastian-ubs commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

@merchako TLDR: this fix just aligns command-based components with the rest of the app and as an unplanned fix cannot change anything on top at the moment.

I agree that row height and OS specific settings would be a win, but this is not what this fix is focusing on. Instead this fix is for "there are no scrollbars visible at all, ever" for this component(s). Better handling of scrollbars should be targeted across the app, where it also happens in other places (e.g. menus, panels, popovers, dialogs, ...), but this is only a little point fix for all command-based components.

Not sure if macOS does currently show scrollbars there on hovering (this is what we finally want across OSes, but needs more general implementation). At least Windows - because of the css class - does not show any scrollbar on that component ever and this is what the current fix is about.

@Sebastian-ubs
Sebastian-ubs force-pushed the re-add-scrollbar-to-command branch 2 times, most recently from 0ea7dab to 05e785e Compare July 16, 2026 10:33
@merchako

Copy link
Copy Markdown
Contributor

Ok, go ahead then

@Sebastian-ubs
Sebastian-ubs force-pushed the re-add-scrollbar-to-command branch from 05e785e to 96f1095 Compare July 17, 2026 14:35
@Sebastian-ubs
Sebastian-ubs enabled auto-merge (squash) July 17, 2026 14:41
@Sebastian-ubs
Sebastian-ubs merged commit 091bebf into main Jul 17, 2026
6 of 7 checks passed
@Sebastian-ubs
Sebastian-ubs deleted the re-add-scrollbar-to-command branch July 17, 2026 15:05
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.

3 participants