The stack property in the Kendo Area Chart does not honor groups as separate stacking contexts.
Instead, everything gets stacked together if `stack: true` is applied.
For other chart types you can overcome this instead of just stack: true, set different stack groups, such as "A" and "B", so they do not stack together.
series: [
{field: "value",
categoryField: "year",
name: "United States Group 1 - Series 1",
stack: "A", // Separate stack group
opacity: 0.5 // Transparency for visibility},
{field: "value1",
categoryField: "year",
name: "United States Group 1 - Series 2",
stack: "A" // Part of the same stack as the first one
},
{field: "value2",
categoryField: "year",
name: "United States Group 2 - Series 1",
stack: "B" // A different stack group
},
{field: "value3",
categoryField: "year",
name: "United States Group 2 - Series 2",
stack: "B" // Part of the second group stack
}
]
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.
Bug report
This is a continuation of the following issue.
Probably related to:
https://source.chromium.org/chromium/chromium/src/+/62d86ddddc8fad157321e42e2acdb18b6ebba951
Reproduction of the problem
- Open the following Dojo in a browser running under the Chromium engine.
- Notice that there is a an console error which showcases sporadically, indicating the following.
Current behavior
The animation container's aria-hidden attribute causes a console error in Chrome and Edge.
Expected/desired behavior
The animation container's aria-hidden attribute should not cause a console error in Chrome and Edge.
Environment
- Kendo UI version: 2024.4.1112
- Browser: [Chrome, Edge]
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();
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.
The same way it is possible to make the search case-insensitive by setting columns.filterable.ignoreCase to true, it would be great if there was a way to add a custom filter (e.g. make the search diacritics-insensitive, with a custom function or as part of provided functionality). Thanks in advance.
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;
}
It will be really useful if we could include a new 'filtering mode' in which operators like 'and' or 'or' are allowed in the filtering input box.
For instance, using the "doesnotcontain" with 'march or july or september' will allow users to exclude multiple conditions in a single filter
In my application, I have grids with dozens of hidden fields.
It would be beneficial if I could filter the available columns similar to what's available in the Windows Forms column chooser:
The mentioned type is still missing for:
- kendoAvatar
- kendoCheckBox
- kendoListView
- kendoOrgChart
- kendoRadioButton
Hi,
We have some multiselect controls which can have a large number of values, and selected values. This causes an issue where the height becomes unreasonably large compared to other controls.
For a typical example of the issue, see here: Multiselect height issue | Kendo UI Dojo
As can also be seen in the provided example, setting max-height with an overflow isn't a viable solution as then it becomes very difficult to see what has been selected - the vertical scroll is much too quick (at least it is using my mouse which has discrete scroll values). Also, there are both dropdown buttons and scroll buttons which is ugly and confusing for end users.
Our suggestion to resolve this would be to add an option for a "single line mode" so that functionality is not broken for other clients. When using this mode, all the items will be kept in a line. In the event of an overflow, then you could either a) cut off the items with an ellipsis "..." or b) enable horizontal scrolling (ideally without a visible scrollbar).
See this example in the DevExpress controls for an example of horizontal scrolling in "Single line mode".
JavaScript/jQuery Tag Box - Overview | jQuery/JS Example
You can see that when all the items are selected, the height is kept consistent. It is still reasonably easy to read as you can easily scroll along.
Something similar to this solution would be ideal for us.
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.
Would like to request that the ability to set a 'CenterTemplate' be added to the Radial and Linear Gauge charts. We show a percentage based label using jquery by appending to the chart wrap a label to show 'x of y (z%)'. What we've seen is that when you go to export the chart, this label doesn't follow with it.
When using other charting types, for example the Arc Gauge or Circular Gauge, they do have a property called 'CenterTemplate' which allows us to do labels like above and have it export correctly.
Can the property be added to other Charts so that we can customize a label to show information such as percentage based text?
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.
When using a grid against a large table with server side filtering (ToDataSourceResult) ToDataSourceResult builds a SQL query that converts the search string to UPPER() and therefore prevents the database from using its indexes. As SQL comparison is case insensitive that LOWER() is unnecessary. As we have may grids where this is an issue it would be time consuming to build out manual filters for each grid instead of using ToDataSourceResult This was discussed here and there was no solution at the time: https://www.telerik.com/forums/grid-filtering-on-text-using-lower-in-sql I would liek to request an option to tell ToDataSourceResult() not to use LOWER() in the sql? See ticket #1339310
Requesting a modification to any component that uses k-animation-container.
Some components have this capability:
popup: {
appendTo: $("SOME ID")
}This gives us the ability to modify CSS for a single/particular popup. Please add this ability to all relevant components.
Or any other method to modify the styling of a particular dropdown. In some cases, there's an ID that's added but is removed for some reason when adding a certain configuration.
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]