In Version 8.9.3 Is anyone else not seeing the ability to change column widths?
thanks
Rod
Best Answers
-
Tom_Hendricks Customer Super IT Monkey ✭✭✭✭✭The issue is described pretty well, here (3 years ago): https://www.telerik.com/forums/resizable-does-not-work-when-too-many-columns-overflows-the-grid
There was no workaround listed in the PR last time I looked earlier this week, but here is a quick hack you could put in your custom.js:var grid = $('div.grid-container.k-grid').data('kendoGrid'); grid.setOptions('scrollable', true); //The whole table will collapse down to a single row grid.refresh(); //This will restore the proper grid size, and columns can now be resized, even after the data refreshes
Edit: It is worth pointing out that this is just a demonstration / should not be added to your prod. It will break the tabs on the My Work grid and cause some undesirable formatting. But it does fix this particular problem.
Although I am sure it would not be supported, you could probably find the controller file where this grid is defined, search for "scrollable: false" and change it to "scrollable: true" so that this is set correctly when the grid is first built, but I did not find that after a very quick search.
6 -
Ryan_Lane Cireson Support Advanced IT Monkey ✭✭✭I encountered the same resizing issues in the different grids after updating to 8.9.3.2012 and was able to determine that the primary cause is that the grid resize handle element created by Kendo was not adapting properly to the additional headers added in on the portal. I changed the grid resize handle's background-color to red to show that the handle is being created but not being offset properly so chances are you'll miss it when hovering:
By overriding the CSS top property for the resize handler and rearranging the order it is added to the DOM I was able to resolve positioning issues:
To be safe instead of modifying the original kendo.all.min.js file I have instead copied the file to the CustomSpace folder and created a redirect in IIS:
kendo.all.min.js (CiresonPortal\Scripts\kendo\2018.1.117\kendo.all.min.js):Original Function Call In _createResizeHandle: t.append(f) Replacement Function Call In _createResizeHandle: t.find("table.k-selectable").before(f)
Note: performing a search for k-resize-handle-inner should bring you to just before the string to replace.
custom.css (CiresonPortal\CustomSpace\custom.css):<div>.k-grid-header .k-resize-handle, .k-grid>.k-resize-handle {</div><div> top: inherit !important;</div><div> background-color: #FF0000;</div><div>}</div>
8
Answers
There was no workaround listed in the PR last time I looked earlier this week, but here is a quick hack you could put in your custom.js:
Edit: It is worth pointing out that this is just a demonstration / should not be added to your prod. It will break the tabs on the My Work grid and cause some undesirable formatting. But it does fix this particular problem.
Although I am sure it would not be supported, you could probably find the controller file where this grid is defined, search for "scrollable: false" and change it to "scrollable: true" so that this is set correctly when the grid is first built, but I did not find that after a very quick search.
By overriding the CSS top property for the resize handler and rearranging the order it is added to the DOM I was able to resolve positioning issues:
To be safe instead of modifying the original kendo.all.min.js file I have instead copied the file to the CustomSpace folder and created a redirect in IIS:
kendo.all.min.js (CiresonPortal\Scripts\kendo\2018.1.117\kendo.all.min.js):
Note: performing a search for k-resize-handle-inner should bring you to just before the string to replace.
custom.css (CiresonPortal\CustomSpace\custom.css):
Confirmed both the issue and the fix. It appears that my "fix" was merely forcing the DOM elements to load in a favorable order (and causing utter havoc along the way, as I warned).
This is an excellent workaround, but should also make it a much simpler matter for Cireson to write a permanent fix.
Do you have any status on this one? https://support.cireson.com/Problem/Edit/PR76978/