The combination of Stacked Headers, Grouping and normal Filter seems to mess up the head column widths. Using 20.3.0.57.
In my case:
Hi Phil,
Greetings from Syncfusion support
We have confirmed this as an issue and logged the defect report “ Column header widths broken, when Group and Filter on” for the same. Thank you for taking the time to report this issue and helping us to improve our product. At Syncfusion, we are committed to fixing all validated defects (subject to technological feasibility and Product Development Life Cycle) and this fix will be included in our upcoming patch release. You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.
https://www.syncfusion.com/feedback/39478/column-header-widths-broken-when-group-and-filter-on
Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization”
Regards,
Prathap S
We are glad to announce that our Essential Studio 2022 patch Release v20.4.0.44 is rolled out and is available for download under the following link and we have included fix for the issue “ Column header widths broken, when Group and Filter on.” in our patch release (20.4.0.44).
NuGet : https://www.nuget.org/packages/Syncfusion.Blazor.Grid
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.
Thanks,
Yes, that does seem to have fixed the reported problem, mostly!
The stacked column headers are now laid out OK, but the column chooser now has problem, as it is displaying blank, selected columns.
Note, in the attached example, there are NO non-displayed columns between Seq & Close, where these 5 blank entries are being shown.
It doesn't do this without stacked columns, so still a stacked columns problem.
Regards,
Phil
We understand that the column chooser feature is currently displaying blank, selected columns .We have reviewed your issue and have created a sample based on the issue you reported in our recent version (20.4.0.44), but we were unable to reproduce the issue. We have included a screenshot and sample for your reference.
|
In order to assist in troubleshooting the issue, we kindly request that you provide a simple reproducible sample or if possible, try modifying the attached sample to see if the issue can be reproduced there. We appreciate your cooperation and hope to resolve this issue for you as soon as possible.
I'm not sure if you did anything to fix this, but I didn't, and its now fixed. I suspect an update in one of the recent releases must have addressed this issue,
My example is no longer showing the errant entries in the column chooser, so OK to close this one off.
Thanks,
Phi
Thanks for the update,
This forum has been marked as closed. If you are experiencing any problems, please share a reproducible sample of the problem and we will proceed further.