Header cell collapses when resizable set to true and promoted to staging environment
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start with the quick-start example linked in the issue, adding resizable: true to the column data or defaultColumnOptions on DataGrid. Compare the local and staging behavior and identify why the header cell collapses only after deployment; done means the header expands to fill the column in both environments.
Written by the indexing model from the issue text.
Description
Describe the bug
When resizable is set to true the columns work as intended but only locally. When the code is deployed to staging environment the header cells shrink. The same problem is seen with code from quick start and other examples.
To Reproduce
- Apply the code from the quick start page but include 'resizable: true' in column data. Alternatively set 'resizable: true' in defaultColumnOptions within the DataGrid component.
- Run locally and confirm expected behavior.
- Deploy to staging environment, header cell will have collapsed.
Link to code example:
https://www.npmjs.com/package/react-data-grid/v/7.0.0-beta.42 for quick start code
What the header cell looks like in local dev environment:
What the header cell looks like in staging environment:
Expected behavior
Header cell should expand to fill the entire width of the column. Expected behavior is seen in local environment but not in staging.
Environment
react-data-gridversion: 7.0.0.beta42react/react-domversion: 18.2.0
Additional context
- Dominant language
- TypeScript
- Stars
- 7.7k
- Forks
- 2.2k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 Comcast/react-data-grid
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Comcast/react-data-grid#4045 ·
Maintainers usually reply within 1 day
-
[Bug] Duplicate frozen column elements in DOM and key collision warning when enableVirtualization={false}Possibly taken @nstepien claimed this 71 days ago. Open
Comcast/react-data-grid#4120 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Comcast/react-data-grid#4004 · 4 comments ·
Maintainers usually reply within 1 day
-
Pinned Rows APIOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Comcast/react-data-grid#3940 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Comcast/react-data-grid#3929 ·
Maintainers usually reply within 1 day
All issues in Comcast/react-data-grid
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
farbenmeer/tapi#531 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
naver/egjs-flicking#971 ·
-
Renderer treats a sub-pixel width difference as a resize, which cancels the `motion()` entranceOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Tenant
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
MTES-MCT/Dossier-Facile-Frontend#2061 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
backnotprop/plannotator#1784 ·
Maintainers usually reply within 1 day