-
Notifications
You must be signed in to change notification settings - Fork 161
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
igx-grid: Cannot set grouped column width in percentage. #4155
Comments
Hello @mkamiishi , |
Hi @ddincheva, I now understand that widths of child headers are calculated based on the parent header width. The header layout I was looking for with the attached sample is this: I changed the html like below, but now the grid shows a horizontal scrollbar. <igx-grid [data]="datasource" [autoGenerate]="false" [width]="'600px'" [height]="'300px'"> I would like the sum of all the column headers to be 100% of the grid width. How am I supposed to define a grid like this? |
Hello @mkamiishi , |
I wanted to provide a brief update of this requirement based on the discussion that we had with @radomirchev and @rkaraivanov. There are scenarios when having both parent and child columns set in % will cause inconsistencies and we cannot guarantee that the result will be what's expected by the end-user. We could consider the following behavior though, |
There has been no recent activity and this issue has been marked inactive. |
After resolving the following issue #5486 , the igxGrid now support setting column widths in both pixels and percentage.
|
Thank you @ddincheva for the thorough research and explanation. This decision is based on the discussions that we had with @radomirchev and @rkaraivanov. @mkamiishi if you have any questions or concerns do let us know. |
Description
Cannot set grouped column width in percentage.
Steps to reproduce
Run the attached sample.
Result
Column width is not correct for col2 and col3.
Expected result
Column width should reflect the values set in width property.
Attachments
igxGrid.zip
The text was updated successfully, but these errors were encountered: