Usability enhancements to the reports framework

Open
#172 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by examining the reports framework and its table layout behavior. Review how horizontal and vertical scrolling, text overflow, and column sizing currently work. Done means reports support freezing row and column headings, optional text wrapping, and resizable columns without losing a usable layout.

Written by the indexing model from the issue text.

Description

Hi,

I propose the following enhancements to the reports framework.

  1. Freezing of rows and columns - esp for large reports with horizontal and vertical scrollbar it is difficult to get the context of a cell without seeing the row-heading and first column. This is similar to the freeze functionality in spreadsheets and would enable easier online review of report data within the system
    image

  2. Wrapping around of text - have an option to wrap around text instead of cutting it when the column width is reached. Maybe the default could still be to cut text if it exceeds column width , but having the option to wrap around is sometimes useful when the text is only slightly longer than column width.
    Please find the attached reference: for ex: description field(dot should not be visible, instead increase the width)
    image

  3. Changing column width - having an option to resize the column width. Sometimes based on text the columns needs to be widened / narrowed down to give a better layout for the whole report

can these above mentioned features be implemented in the upcoming release.

Thanks

Dominant language
JavaScript
Stars
1.3k
Forks
223
Avg merge
23h 14m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from frappe/datatable

All issues in frappe/datatable

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.