-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Header cell collapses when resizable set to true and promoted to staging environment #3463
Comments
I face the same issue, I am using Next.js version 14.0.0 and react-data-grid version ^7.0.0-beta.42 |
Hey @ronneldavis @FoxCDD are you guys still facing the same issue, I was not able to find the issue as mentioned by you. |
This is happening to me as well. In my production build, several CSS layers are missing (rdg.MeasuringCell, rdg.GroupCellContent, rdg.SortableHeaderCell, rdg.SortableHeaderName). I use Webpack 5 for my build process. The production build uses the MiniCssExtractPlugin loader, while development uses style-loader. As a temporary workaround, I was able to fix the issue by removing MiniCssExtractPlugin and using style-loader instead. |
Yes I'm still facing this issue. I also found that setting sortable to true also caused the same issue. |
Yeap still facing the same issue, I have sortable and resizable set as true in the default column options. defaultColumnOptions={{
sortable: true,
resizable: true,
}} |
setting react: |
Same issue, works fine in dev but not when deployed. |
I'm having the same problem. I checked and it's happening since 7.0.0-beta.42. I did not experience this issue with 7.0.0-beta.41. |
Wonder if its something to do with this commit: |
I experienced this issue today as well, and just wanted to share some extra data in case it helps. In my case, the issue from 2 classes being applied to the columnheader div from the rdg.HeaderCell layer (.c1creorc7-0-0-beta-42, .c1kqdw7y7-0-0-beta-42). They both show as applying the same styles, which includes "inline-size: 10px": But if you look at the stylesheet, those properties are from a different class (r1y6ywlx7-0-0-beta-42) in the same layer, but not in .c1kqdw7y7-0-0-beta-42 or .c6l2wv17-0-0-beta-42: No idea why they are being applied here, the div in question doesn't have the r1y6ywlx7-0-0-beta-42 class on it, and these properties are clearly only in that class and not in the ones actually being applied to that div. I also just worked-around it by using .41. Just sharing in case it helps with identifying the issue. |
This worked on my end. Thanks @c-stiles |
Any news on this ? It is still happening. This bug was introduced on the version |
Same issue for me. Local is fine, but Webpack build artifacts are collapsing several different css styles into a grouped one. I don't have a good workaround, but oddly, the order of the source css rules has an impact. It's definitely something happening in post-processing and new in beta 42
becomes
|
Any news on this ? It is still happening. |
This is key of the problem. My temp solution would be simple and no need to change the webpack config:
Note: Do not import styles.css in your source file using import. |
same with me 7.0.0-beta.41 works fine but 7.0.0-beta.42 is having this problem. |
still happening as of version 7.0.0-beta.47. Do anyone find any solutions? |
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
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-grid
version: 7.0.0.beta42react
/react-dom
version: 18.2.0Additional context
The text was updated successfully, but these errors were encountered: