Many Kendo UI Widgets support enabling/disabling animations via their options. In our case, we always disable them. As of R1 2023, the toolbar widget does not support customizing or turning off animations and always slides in/out the options of splitButtons or the overflow menu.
To maintain a consistent look&feel, disabling animations should by supported by the toolbar as well.
Do you have any suggestions how this could be fixed in the meantime?
The DropDownTree allows us to configure its checkChildren and filter options. Both options are working correctly, when used separately.
When the two options are defined for the DropDownTree, the checkChildren options don't select the child elements of a given node that is checked.
Only the "Furniture" checkbox is being checked
The "Furniture" and all of its child nodes should be selected when clicking on the "Furniture" checkbox.
Here is a Dojo example in which the checkChildren configuration is working as expected.
In a Grid with popup editing, saving/cancelling the changes shows hidden columns for a short time.
Regression with v 2023.2.829
The hidden ID column is shown for a short time
The hidden column should remain hidden
In the latest version of Kendo UI, various input controls like the NumericTextBox or the ColorPicker now consist of an input field and a button control (used for increasing/decreasing the value or opening the dropdown).
The border-radius for those widgets can be controlled by setting the "rounded" option. At the same time, when using SASS themes, a button's default border-radius might be set using the $kendo-button-border-radius variable. The buttons inside e.g. a NumericTextBox do not override the theme's border-radius which leads to an outcome like this:
Widgets that use Buttons internally (and therefore offer no way of overriding the button's border-radius by setting its "rounded" option manually) should override the default styles.
Unfortunately, I could not reproduce the behavior in a DOJO, because I cannot transpile SASS themes there.
I have noticed that, after switching themes, the tooltips in our application do no longer work correctly. I was able to reproduce the issue in the following two DOJOs:
The only difference between those two is the stylesheet to be loaded (line 6).
Steps to reproduce:
In step 4, the correct behavior would be displaying the tooltip in the same fashion as in step 2. However, in the faulty DOJO, it can be seen that the tooltip does not expand past the width of the text that is displayed when hovering over the green dot. This means that when displaying long tooltips after short ones, they are always wrapped unnecessarily.
A way to fix this behavior (and what's actually the difference between the two stylesheets) is to set the position on the ".k-animation-container" back to its default value "static". Usually, this value is overridden by the output of the size calculations, but during the calculations this value comes to play.
This third DOJO demonstrates the fix described above.
Please note that when using the default-ocean-blue stylesheet, the positioning of the callout seems to be broken as well.
Consider the following scenario: There is a sortable Kendo-UI grid with a corresponding dataSource. Initially, the dataSource contains some items. When updating the dataSource to an empty array, all items disappear from the grid - so far, so good. However, if a column header is clicked afterwards to sort that column, the removed data reappears again.
We created a small "walkthrough" in this DOJO to demonstrate the issue.
FYI: The issue can be avoided by using a custom implementation of dataSource.transport.read which always returns the latest data.
Our clients are requesting that the search in the multiselect look like the search in the dropdownlist. They want it to be in the list that opens rather than in the value box and want a consistent operation and look. This should be an option that can be set when initializing the multi-select. I attempted this using the forum post below but it is quite buggy and requires a lot of modifications.
https://www.telerik.com/forums/make-filter-in-multiselect-look-like-filter-in-dropdownlist
Bug report
DropDownTree as a row editor does not clear chips when x button is clicked. Select All option does not select items
this.dataSource.data() does not have items
Regression with 2022.1.119
Reproduction of the problem
Open this Dojo example - https://dojo.telerik.com/oXizEQac
Open Name column row filter DropDownTree
Select All shall select all items. Clearing items shall clear them
Environment
Kendo UI version: 2022.1.119 or newer
Browser: [all]
Context: There is an item that illustrates the issue here: https://www.telerik.com/forums/kendo-datepicker-value-not-populated-after-refresh-firefox-only
In Firefox, when using the asp-for tag helper to bind a c# DateTime field to an input element, then calling kendoDatePicker() on that element, the control fails to populate on a soft-refresh (F5). Upon reloading using F5 in Firefox, the input's type is set to datetime-local, and the input 's control variation is changed to the default date picker. Then, the Kendo UI DatePicker is initialized with a blank input which normally has a type of text.
Example project and video of issue are attached.
This is the pertinent code (also happens in latest version of Kendo as well):
public class IndexViewModel
{
public DateTime DateAsDateTime { get; set; }
}
public IActionResult Index()
{
return View(new IndexViewModel { DateAsDateTime = DateTime.Today });
}
@model IndexViewModel
<input id="dtDate" asp-for="@Model.DateAsDateTime">
<script type="text/javascript">
$(document).ready(function () {
$("#dtDate").kendoDatePicker();
});
</script>
I have a chat widget configured like this:
let chat = $(target).kendoChat({ messages: { placeholder: ResourceManager.GetInstance().getResource("SR_TYPE_A_MESSAGE") }, user: user, post: async (m: kendo.ui.ChatPostEvent) => await this.post(m), }).data("kendoChat");
If the post handler tries to await a call to a web service (to do some translation/tag substitution) then the message is posted to the chat and the results of the web call are ignored.
If you have several Inline Editors and a Slider, switching focus from Slider and typing in the Editors result in an error in the console.
An error is thrown in the console
No error should be thrown on the console
multiline message is a basic feature that Kendo Conversational UI should have..
The current chat widget renders the user-input as an INPUT control, which means it cannot support multi-line support.
Wish for the option of rendering a TEXTAREA control instead of an INPUT for the chat widget:
Something like the following:
let chat = $(target).kendoChat({
messages: {
placeholder: ResourceManager.GetInstance().getResource("SR_TYPE_A_MESSAGE"),
textarea: true
},
user: user,
post: async (m: kendo.ui.ChatPostEvent) => await this.post(m),
}).data("kendoChat");
When the loaderType is set to skeleton and the user edit the cells in the Grid, when saving the Grid is displayed empty.
The Grid does not display any data. The Grid is displayed as expected when the default loaderType is set.
The updated data should be displayed
sync: function(e){
$("#grid").data('kendoGrid').refresh()
},
The Kendo Spreadsheet is bound to a Kendo datasource, the datasource defines a schema, but when the JSON comes back the spreadsheet just ignores the schema properties and dumps the entire thing into the sheet.
It would be nice to not have to code up some additional workaround after already having defined the schema I want.
(No control over the JSON structure from the server)
I have noticed some weird behaviour when using the SwiftKey keyboard on Android.
To recreate:
- Install SwiftKey keyboard and enable
- browse to https://demos.telerik.com/kendo-ui/dateinput/index in chrome for android
- Select year component of date input control
- type 1 - year shows as 0001 - correct
- type 9 - year shows as 0019 - correct
- type 7 - year shows as 0009 - incorrect
- type 5 - year shows as 0019 - incorrect
All the other keyboard i have tried work as expected, i appreciate that this is a non standard keyboard on Android however it is a widely used one and works as expected when typing 1975 into any other app / control on the device.