When a user edits a cell/row and presses enter, the cell is marked as dirty. However, the Save and Cancel buttons remain disabled, thus the user should focus on a different cell before being able to save changes.
The cell is closed and marked as dirty, the 'Save changes and 'Cancel changes' buttons remain disabled.
The buttons should be enabled once the cell is marked as dirty.
cellClose: function(e){
e.sender._toggleToolbarEditingItemsVisibility()
},
I have an event template. Inside this template I am using a MultiSelect. It is defined like: <select data-down-Arrow="true"… . The downArrow property does not work. I discovered via debugging the kendo.all.js file the problem. Fortunately this one is fixable outside that file:
Hi team,
I think there is a bug in the dependency detection.
In the attached "config_buged.js" i have chosen some components. The component "chiplist" was partially checked due to dependency.
When lunching my application I got the error :
Message: e(...).kendoChipList is not a function
at init._createList (kendo.custom.min.js:91:8505)
at new init (kendo.custom.min.js:91:3218)
at init._attachGroupable (kendo.custom.min.js:133:96797)
at init._groupable (kendo.custom.min.js:133:96348)
at init._continueInit (kendo.custom.min.js:133:33864)
at new init (kendo.custom.min.js:133:33735)
at HTMLDivElement.<anonymous> (kendo.custom.min.js:1:42737)
at jQuery.each (jquery-3.1.1.js:368:19)
at jQuery.fn.init.each (jquery-3.1.1.js:157:17)
at e.fn.<computed> [as kendoGrid] (kendo.custom.min.js:1:42713)
I was forced to totaly check the "chipList" component as seen in the attached file config.json
This is a continuation of the following issue.
Probably related to:
https://source.chromium.org/chromium/chromium/src/+/62d86ddddc8fad157321e42e2acdb18b6ebba951
The animation container's aria-hidden attribute causes a console error in Chrome and Edge.
The animation container's aria-hidden attribute should not cause a console error in Chrome and Edge.
Hello!
Prior to 2024.2.514 (2024 Q2), the DateRangePicker would "force users first to select start and then end range regardless of the date input selected" [1,2]. However, with the latest 2024 Q2 release, clicking the End input on the DateRangePicker selects the range end.
I did not see this specifically mentioned in the release notes, https://www.telerik.com/support/whats-new/kendo-ui/release-history/kendo-ui-for-jquery-2024-2-514-(2024-q2), so I am reporting this as a bug.
Here is a basic Dojo to demonstrate: https://dojo.telerik.com/IWAbUpuV. You can see the previous behavior by changing the library to the previous version (2024.1.319).
The Kendo-UI Diagram widget supports moving the whole diagram using the pan() method. However, the given offset does always have to be absolute.
Consider the following example:
The diagram is zoomed in and therefore not fully visible - assume a current offset of (-100, -100). The users should be able to pan using keyboard shortcuts. Whenever pressing one of the arrow keys, the diagram is moved in the corresponding direction by e.g. 50px:
If the user presses [ArrowRight], pan() needs to be called with an offset of (-50, -100).
If the user presses [ArrowUp], pan() needs to be called with an offset of (-100, -150).
However, since I do not know how much the diagram has already been moved, I cannot set the absolute offset required.
I have seen that pan() returns the current offset when being called without arguments, but this is not documented. Is this safe to use for that purpose or is there a better alternative? If yes, the documentation should be updated.
Example: https://runner.telerik.io/fullscreen/yypoqSea
This example is based on the example from the docs with `navigatable: true` and enough data that the user needs to scroll in order to see the bottom row.
On Chrome on macOS, the filter menu cannot be used when `navigatable: true` and "Tap to click" is enabled in the macOS Trackpad settings. When clicking on the filter icon, the menu disappears very quickly (see screen recording). As a workaround, setting `navigatable` to false seems to resolve the problem. The same issue does not seem to occur on Safari, however, there is still odd behavior with the scrolling.
For some reason, screen size, resolution, and window settings impact the ability to reproduce the issue. The most reliable way for me to reproduce the issue was with Chrome in full screen on a 16-inch MacBook (13-inch works too) with the bookmarks bar showing and no external displays connected. Hiding the bookmarks bar or not using full screen seems to make it more difficult to reproduce.
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;
}
The mentioned type is still missing for:
- kendoAvatar
- kendoCheckBox
- kendoListView
- kendoOrgChart
- kendoRadioButton
Hi Guys,
Just upgrade to the 2025.1.211 release and during testing I have spotted a fundamental issue which should have been picked up during QA.
Run the following dojo
https://dojo.telerik.com/dBSXoLYq
Open up the filter menu on the date column and hit the icon and you will find the date pop-up is constrained within the filter menu and cannot be navigated.
See attached screenshot - DateFilter.png
Note: This also effects filtering Date Time columns as well
Is there a workaround for this or do we have to wait another couple of months for the next release because as things stand we cannot pushed this to production.
Regards
Alan.
See demo page: https://docs.telerik.com/kendo-ui/api/javascript/ui/colorpicker/configuration/clearbutton
The example uses "<input id="colorpicker" type="color" />". Opening the preview reveals a black color.
Change the input-tag to div and the 'clear'-style is presented in the preview.
Or remove the color type when using the input-tag: "<input id="colorpicker" />" also correctly represents clear.
I can also locally reproduce it with Kendo UI jQuery v2024.4.1112.
Line Chart Crosshair doesn't display on Tablets.
Display's fine on Desktop & also on Mobile, but tested on iPad and Android tablets the Crosshair line does not display.
kendo.2020.1.114
Bug report
Line Chart Crosshair doesn't display on iPad iOS 17
Reproduction of the problem
Dojo: https://dojo.telerik.com/mGtuUvac
Expected/desired behavior
Crosshair shall display on tap
Environment
Browser: [all]
https://dojo.telerik.com/yBSdUQYS demonstrates the issue:
When a grid detail row is expanded, and pushUpdate() is called on it, the row collapses.
What is expected is for the grid row to remain in its prior state (expanded or collapsed.)
Until this is fixed, is there a work-around, other than manually re-expanding the detail row(s)? This is not a feasible work-around in which multiple nested grid rows are collapses and re-expanded, as this causes the UI to jump unexpectedly for the user.
There is an issue with the .k-sorted class being applied to the last column in the grid when the actual column is not visible. It also is not updating the k-sorted when a sort is applied after the grid was created.
This seems to be an issue in the latest release if the column sorted on is hidden, the last column in the grid gets the class. I also noticed that sorting a column does not apply the k-sorted class to the correct column: https://dojo.telerik.com/@dojolee/eFIbaSUn
Hi,
We are facing issue on every popup and context menu open. aria-hidden property has been set to true by default while rendering the control.
Blocked aria-hidden on an element because the element that just received focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor.
var chart = $("#chart").data("kendoChart");
var series = [];
$(theData.Serieses).each(function (index) {
series.push({
name: theData.Serieses[index].Name,
field: theData.Serieses[index].Name,
data: theData.Serieses[index].SeriesPoints,
xField: "X",
yField: "Y",
color: theData.Serieses[index].Colour,
markers: {
type: theData.Serieses[index].Shape
}
});
});
chart.setOptions({ series: series, noData: series.length == 0 });
chart.redraw();
console.log(chart.options);
When updating a chart after instantiation, because noData defaults to true, the overlay is shown immediately
if you try and set noData via setOptions then redraw(), the overlay is still in place
Honestly, this should have been marked as a breaking change as every single chart has to be updated to force noData to false just to show initially
Hello,
My use case:
On grid dataBound, I am iterating over the table rows to perform some piece of custom logic on the row based off of the backing dataItem. Our production site is using version 2024.1.130, and everything is working great. Our next release we've updated to version 2024.2.514, and when we try adding a record, we get an error; when we try to access the dataItem of the last table-row - the dataItem is undefined. The grid.items() in my case is an array of size 21, and the internal _data array is size 20.
Repro conditions (as far as I can tell):
My workaround:
Simply perform a null check on the dataItem before doing the logic. We are calling DataSource.read in the DataSource.sync success callback anyway, so the grid will reload and the dataBound event will be handled afresh.
I've created the below dojo snippet to demonstrate a simplified version of my use case. I tested with 2024.1.130 and seems to work fine. I noticed the issue starting at version 2024.1.319.
https://dojo.telerik.com/INbSBrSg
A note: No, I don't actually use the internal _data property in my code, just for debugging purposes :)
Thanks!
-Alexa
I'm seeing an error in the Chrome console when the filter menu is clicked on in a kendo grid: https://demos.telerik.com/kendo-ui/grid/filter-menu-customization
You can see the example in the link above by opening your console in Chrome and clicking on the filter button.
Here is the error:
Blocked aria-hidden on a <a> element because the element that just received focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.