Hi I am using on an MVC project the grid autosize functionality successfully (version: R2 2017 2017.2.504.545). Now on another project I have to use the .NET Core (version: R1 2018: 2018.1.117.0) but the autosize functionality does not work anymore. I have investigated the two solutions and it seems that when I use grid.Scrollable(s => s.Height("auto")) it generates "height: auto" instead of the configuration: "scrollable: { height: auto }"
Is this function as design? What are the alternatives to this issue?
4 Answers, 1 is accepted
Thank you for the details and locating the difference in the generated jQuery options.
I can confirm that this is an issue with the current version of Kendo UI Grid.
I created an issue in our GitHub repository and forwarded it to our developers for fixing. You can track its progress at:
https://github.com/telerik/kendo-ui-core/issues/4093
For now, there is no available workaround as the height options is applied initially and can only be modified not removed if one is found it will be added to the GitHub issue for reference.
Additionally, I updated your Telerik points for bringing this to our attention.
Stefan
Progress Telerik
Hi Stefan,
Has this really bean solved?
According to this page
https://www.telerik.com/support/whats-new/aspnet-core-ui/release-history/ui-for-asp-net-core-r2-2018-uiaspcore-2018-2-516
at Grid Fixes appears the text "The scrollable(s => s.Height("auto")) property is not correctly applied to the ASP.NET Core wrapper"
I have downloaded the nuget package version Telerik.UI.for.Asp.Net.Core 2018.2.516 and the problem is not solved.
Has the issue been solved also on the nuget package?
I have tested this on my end and the property was correctly applied in the latest version.
Please check the attached example for reference.
Please have in mind that sometimes file from the older version could be cached and the fix is not loaded.
If the issue still occurs in the real application, please provide an example, so we can inspect it locally.
Regards,
Stefan
Progress Telerik
Hi Stefan,
Sorry about the inconvenience. Indeed after I cleared the nugget cached the issue was indeed solved. Not ideal way but good to know in the future.