logseq / logseq/db-test

'Column visibility' and 'Group by' selection lists cannot be fully accessed in Table View

Open
#1,159 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

In the Table View of a query, the selection lists for 'column visibility' and 'Group by' become difficult or impossible to use when there are too many available options.

### Reproduce the Bug

1. Create or open a query with a large number of properties.
2. Switch to Table View.
3. Open the 'column visibility' or 'Group by' menu.
4. Add enough properties/options so that the selection list becomes longer than the available space.
5. Notice that the list cannot be fully accessed.

### Expected Behavior

The selection list should support scrolling when it exceeds the available screen space, allowing all options to be selected.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

logseq 2.0.1

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Table View implementation and reproduce the issue with a query containing many properties. Inspect the column visibility and Group by selection menus, then verify that both lists can scroll when they exceed the available screen space and that every option remains selectable.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.