If you configure a TextArea to be resizable, it simply is not.
This last worked in 2023 R1(2023.1.117): https://dojo.telerik.com/@Stephen/IqePaHim
And is first broken in 2023 R1 SP1(2023.1.314): https://dojo.telerik.com/@Stephen/UWUpoxUw
And is still broken in 2023 R1 SP2(2023.1.425): https://dojo.telerik.com/@Stephen/OnoKiboM
Notice that the resize handle is not even rendered anymore.
If the splitter container has 100%, the height of the Splitter panes is changed when the splitbar is moved to the right or left.
The panes of the splitter have the wrong height when it is moved to the left and the correct one when it is moved to the right.
Splitbar panes should have the same height regardless of splitbar moving.
When the splitbar is moved to the left, the left position of the second splitbar pane should be updated before its width. For now, it is updated after it, which causes showing a horizontal scrollbar of the Splitter parent for a moment. As result, the Splitter pane height is calculated wrongly.
Currently, attributes of an initial element are copied to a dynamically created outer element. This behavior is common for widgets from the "Editors" group (and not only). This causes multiple confusing results as applying styles or classes to the outer and inner elements at the same time. For example in this Dojo sample, when width or height is defined by percentage units, this causes a broken appearance.
Consider removing such attributes from the initial element and keeping them only on the generated outer one. A similar issue is caused when a custom class is applied to the initial element. The class is applied to both elements (outer and inner), so an additional selector should be used to target an exact element.
If you check the applied styles in the browser's DEV-Tools, you can see that the internal class "k-input-inner" overrides the value set using the overflow option.
I have some forms that is bind to MVVM and I am binding the VM's change event to check for any pending changes on the form. The issue I am having is for textarea that is bind to null value, if I tab/click on the textarea and leave without making any changes, it will still trigger the VM's change event.
What is the solution for this?