Describe the bug
When the user selects a word and changes its style (for example bold, italic, etc.) the content of the inline Editor is wrapped on multiple lines.
To reproduce
Steps to reproduce the behavior:
Expected behavior
The content should not wrap.
Workaround
<style>
.k-editor{
display: block
}
</style>
Dojo - https://dojo.telerik.com/iZZPZIGg
Regression since 2022.1.119
Affected package (please remove the unneeded items)
Affected suites (please remove the unneeded items)
Affected browsers (please remove the unneeded items)
When a column in the Grid is configured with a group template, updating a cell doesn't update the value of the group template.
Regression introduced with 2024.1.319
The value of the group template in the Total column is not updated as per the salary column
The value of the group template in the Total column should be updated as it is calculated using the Salary column
In a Spreadsheet that has a scrollable Sheetbar, clicking the arrow icons to scroll the sheets refreshes the page.
Regression introduced with 2024.4.1112
Workaround - https://dojo.telerik.com/IVcuYtjD/5
The page refreshes
The page shouldn't refresh
Bug report
Remove scrollable: true as it overrides theme `overflow: auto`
Reproduction of the problem
Dojo: https://dojo.telerik.com/ZnTQkfKf
Ticket ID: 1680257
Environment
jQuery: 3.7.0
Kendo UI version: [all]
Browser: [all ]
When the Inline Editor is created from a collapsed pane in the Splitter, the toolbar of the Editor is broken.
Regression introduced with 2025.1.211
The inline Editor's toolbar is broken
The Editor's toolbar should be rendered correctly
When attempting to validate a cell value against a predefined finite list, the validation process fails to recognize valid entries that are present in the list. Instead, it incorrectly flags them as invalid. The issue occur when there is an empty space before the first value in the 'from' option.
On the first row, the 'YES' in the B1 cell is marked as invalid although it is present in the list with the valid values. the difference between row 1 and row 4 is the empty space in the validation from configuration:
"from": "{ \"YES\", \"NO\"}", //row 1
"from": "{\"YES\", \"NO\"}" //row 4
The empty space added in the from
configuration option should not affect the validation. If the cell value is present in the list, it should be marked as valid.
When a cell that contains letters and numbers is dragged and dropped, the new content has an incorrect value. The issue appears when the first character is a letter and when the number contains zero.
The result should be the same value in case of text content (C0) or an incremented value in case the content ends with a number. Ex: A101 should result in A102, A103, A104 etc.
When the Spreadsheet height is greater than the page height and the user scrolls and than enters a value in a cell, the Spreadsheet scrolls to the top.
The Spreadsheet is scrolled to the top. screencast - https://go.screenpal.com/watch/cZj220V9U6j
The Spreadsheet should persist the position.
I find the documentation is critically lacking with regards to the available options for a feature. Here is an example of what I mean... http://docs.telerik.com/kendo-ui/api/javascript/dataviz/diagram/layout#configuration-alignContent The diagram Layout > alignContent feature "Specifies the alignment of the content." Ok, but the documentation does not even say what the allowed values are. Instead, it just has "alignContent String (default: "start")". Now, I guess the allowed values here are the same values allowed for an SVG text-anchor. https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/text-anchor How about adding those possible values to the api documentation, or including a link to the relevant area of the SVG specification? Hope this makes sense.
Bug report
Error is thrown in the console when an event is dragged.
Reproduction of the problem
Dojo: https://dojo.telerik.com/ORuSEYoW
Expected/desired behavior
Error shall not appear
Environment
Kendo UI version: [all]
jQuery version: [all]
Browser: all
Pie and Donut Chart can not be exported to PDF, Png or Jpg
The pie and donut charts are missing.
The Charts should be exported to the selected file format
There are many properties that can be set during initialization that cannot be changed through the API afterwards. Take the Kendo UI ToolBar for example. You can add a button to the toolbar and set the text, but you cannot change the text afterwards unless you update the element directly. It may seem like a simple thing to change the text of an element, like so: $("#myButton").text("New Text"). However, if you had set the imageUrl as well, setting the text like I did above would remove the image. Knowing that, you could get the text node and update the nodeValue. That may work today but could easily be broken during a Kendo UI update (for example, if the update included a change that wraps the text in a span). Having to deal with native elements after they have been created by the Kendo UI components is a dangerous practice for developers as it requires an internal knowledge of how elements are rendered based on the different options set. As mentioned above, it is also dangerous as any update could break our code. Therefore, it is imperative to expose methods that allow us to modify any properties through the API (where possible) to allow us to create clean and easy to maintain code. If you search the feedback, you will see many requests to add a method here and a method there. There is even a related one to this called "Kendo Mobile: Methods to set properties dynamically". Suggestion: When you have child elements, such as buttons on the toolbar, please allow us to update those widgets directly rather than through the parent. For example, instead of $("#myToolbar").data("kendoToolBar").enable("#myButton"), allow us to do something like this $("#myButton").data("kendoToolBarItem").enable();
When there are multiple Forms on the same page, submiting one of the Forms triggers the other Forms validation.
The first Form is also validated and the field is marked as invalid.
Only the Form which button has been clicked have to be validated.
When the DropDownList component is configured with Adaptive Mode and Filtering, opening the dropdown on a mobile device and attempting to type in the search field causes the popup to close immediately.
With Adaptive Mode and Filtering enabled, the DropDownList popup closes immediately when tapping the search field on a mobile device.
The DropDownList popup should remain open when tapping the search field on a mobile device, allowing users to enter text and filter options.
1678876
In the DropDownList component with filtering, opening the dropdown on a mobile device and attempting to type in the search field causes the popup to close immediately.
Regression introduced with 2025.1.211
The DropDownList popup closes immediately when tapping the search field on a mobile device.
The DropDownList popup should remain open when tapping the search field on a mobile device, allowing users to enter text and filter options.
We have a need to be able to provide a dropdown above the scheduler, in order to allow the end user to change the time zone of the scheduler dynamically, even after it has been initialized. Our team was disappointed that this is currently not possible (http://www.telerik.com/forums/timezone-dropdown), but maybe in the future. Thanks for reading.
Enhancement
Expose setOptions() for Kendo Wizard
Desired Behavior
setOptions shall update Wizard steps
wizard.setOptions({
steps: steps
});
Destroy current Wizard and reinitialize with new steps
let wizard = $("#wizard").data('kendoWizard');
wizard.destroy();
$("#wizard").empty();
let steps = [];
for (var i = 0; i < 4; i++) {
steps.push({
title: "Tab " + i,
content: "Tab Content " + i
});
}
$("#wizard").kendoWizard({
steps: steps
});
there is no binding for noData
e.g.
noData?: boolean | undefined;
interface ChartOptions {
name?: string | undefined;
autoBind?: boolean | undefined;
axisDefaults?: ChartAxisDefaults | undefined;
categoryAxis?: ChartCategoryAxisItem | ChartCategoryAxisItem[] | undefined;
chartArea?: ChartChartArea | undefined;
dataSource?: any|any|kendo.data.DataSource | undefined;
legend?: ChartLegend | undefined;
panes?: ChartPane[] | undefined;
pannable?: boolean | ChartPannable | undefined;
pdf?: ChartPdf | undefined;
persistSeriesVisibility?: boolean | undefined;
plotArea?: ChartPlotArea | undefined;
renderAs?: string | undefined;
series?: ChartSeriesItem[] | undefined;
seriesColors?: any;
seriesDefaults?: ChartSeriesDefaults | undefined;
theme?: string | undefined;
subtitle?: string | ChartSubtitle | undefined;
title?: string | ChartTitle | undefined;
tooltip?: ChartTooltip | undefined;
transitions?: boolean | undefined;
valueAxis?: ChartValueAxisItem | ChartValueAxisItem[] | undefined;
xAxis?: ChartXAxisItem | ChartXAxisItem[] | undefined;
yAxis?: ChartYAxisItem | ChartYAxisItem[] | undefined;
zoomable?: boolean | ChartZoomable | undefined;
axisLabelClick?(e: ChartAxisLabelClickEvent): void;
dataBound?(e: ChartDataBoundEvent): void;
drag?(e: ChartDragEvent): void;
dragEnd?(e: ChartDragEndEvent): void;
dragStart?(e: ChartDragStartEvent): void;
legendItemClick?(e: ChartLegendItemClickEvent): void;
legendItemHover?(e: ChartLegendItemHoverEvent): void;
legendItemLeave?(e: ChartLegendItemLeaveEvent): void;
noteClick?(e: ChartNoteClickEvent): void;
noteHover?(e: ChartNoteHoverEvent): void;
noteLeave?(e: ChartNoteLeaveEvent): void;
paneRender?(e: ChartPaneRenderEvent): void;
plotAreaClick?(e: ChartPlotAreaClickEvent): void;
plotAreaHover?(e: ChartPlotAreaHoverEvent): void;
plotAreaLeave?(e: ChartPlotAreaLeaveEvent): void;
render?(e: ChartRenderEvent): void;
select?(e: ChartSelectEvent): void;
selectEnd?(e: ChartSelectEndEvent): void;
selectStart?(e: ChartSelectStartEvent): void;
seriesClick?(e: ChartSeriesClickEvent): void;
seriesHover?(e: ChartSeriesHoverEvent): void;
seriesOver?(e: ChartSeriesOverEvent): void;
seriesLeave?(e: ChartSeriesLeaveEvent): void;
zoom?(e: ChartZoomEvent): void;
zoomEnd?(e: ChartZoomEndEvent): void;
zoomStart?(e: ChartZoomStartEvent): void;
}
Currently, if you focus the command buttons, pressing tab will navigate to the buttons on the next row.
The focus will move to the buttons on the next row.
When the focus is on the Delete button, pressing Tab should return the focus to the current cell so that you can navigate to the remaining cells on the same row.