Hi Doug,

I'm glad to find out you have managed to isolate the scenario that the issue stems from the machine itself.

I will mark this thread's status as "Declined" as it does not actually reports a bug but a corner case on a local machine as clarified.

Regards,
Nadezhda Tacheva
Progress Telerik

Hi Doug,

The attached video from my last post represents the demo page behavior in the latest version of Chrome.

As Telerik UI for Blazor supports the latest versions of the listed browsers (Chrome, Edge, Firefox, Safari - see Browser support), we strongly recommend visiting our resources with the latest possible version of your browser.

As a side note, the new version of Microsoft Edge is based on the Chromium engine (as of January, 2020) and therefore it should function and look like Chrome.

With the above being said, could you please double check if you are using the latest version of your browser? If you do but you are still noticing any odd behavior, could you send us a video of the issue you are experiencing?

Also,  if you are reproducing the described behavior locally as well, could you send us the reproduction code to investigate further?

Regards,
Nadezhda Tacheva
Progress Telerik

Hi Doug,

I tested the resizing behavior in the demo, however it looks to me it behaves as expected (see video attached).

If you experience any delay between the mouse action and the column resizing, that could be caused by some network latency. In order to verify that, you can test it locally to see if it behaves differently.

Apart from the demo use case, we are aware of one limitation of the resizing in scenario with flexbox containers. In case you are referring to a scrollbar appearing on the main app element or the body, instead of the grid/layout container, this behavior stems from the way elements with display: flex handle <table> elements with large width set in % and table-layout:fixed. More details as well as reproduction and solution on that you can find in this knowledge base article - Grid is too wide under bootstrap column, or causes unexpected scrollbars in the layout.

I hope you'll find the above information and details useful. In case additional questions appear on the topic, could you send us a reproduction of the behavior you are experiencing, so we can investigate further?

Regards,
Nadezhda Tacheva
Progress Telerik

Hello Doug,

If I correctly understand, you are referring to the resizing indicator appearing not exactly on the cell border (as it is in Excel for example) but a little bit on the side.

If that's the case, the reason behind that behavior is that the Resize event needs a DOM element to be subscribed to. Since the cell border is not a DOM element as per its nature, we use a span with class .k-column-resizer for that purpose (see the attached screenshot). Therefore, the resizing cursor appears when you hover over this span instead of on hovering on the cell border.

If this is not what you mean, could you provide some more details and, perhaps, a screenshot or video of the problem?

Regards,
Nadezhda Tacheva
Progress Telerik