Usability enhancements to the reports framework
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.
-
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

-
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)

-
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from frappe/datatable
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Datatable stops responding to clicks after selecting across collapsed or scrolled-out rowsPossibly taken @RaphaelFakhri claimed this 24 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
Bug with serialNoColumn= falsePossibly taken @Valley-15 claimed this 295 days ago. Open
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in frappe/datatable
Similar issues
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
HarperFast/rocksdb-js#1131 ·
Maintainers usually reply within 1 day
-
Reveal: resolved but blocked Pending boundary hides its fallbackPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anothaDev/luci-theme-vantage#137 ·
Maintainers usually reply within 1 day
-
Area/DeveloperPortal Aspect/UI Severity/Minor Type/Bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
wso2/api-platform#4369 ·
Maintainers usually reply within 1 day