Search: Allow users to resize-columns width
- Dominant language
- Scala
- Stars
- 301
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Acceptance Criteria:
- Upon clicking on the column header dropdown menu, the user can set the column width:
- The user can slide a cursor between a min and max width (in pixels)
- The value set by the slider is shown in an input box
- The user can change/type the number of pixels instead of using the slider
- The value will be reflected on the slider
- Upon saving, the column will be resized to the new width.

Note:
- This would replace the column width calculation done today and store it to the configuration (separate ticket).
Not in scope:
- The user can click on the border between two columns _headers_ to resize the width of the left one.
- The border between to column header cells will highlight to show that it can be dragged.
- By clicking and dragging the cursor, the width of the left column will change.
- The right column and right side of the table will move accordingly (to the right if the column width is increased, to the left if the width is reduced) but not resize.
- Clicking on the border between the columns in the row space won't have any effects.
- Releasing the cursor, the left column width will be set to the new width.
- The column width should have a minimum width
- When increasing the column width, the increase is limited by the viewport
- If the user scrolls right, he or she can further increase the column width
- The column width is saved for that (temporary) display configuration (or view) for that user.
- Changing the display configuration (or view) or resetting it will affect column widths.
Overlaps: #3180
Contributor guide
Research direction
The issue does not name files or tests; start by locating the search column-header dropdown and the current column-width calculation. Implement the specified slider and pixel input behavior, then verify that saving applies the selected width while keeping the excluded drag-to-resize behavior out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- frontend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100