Currently when calling toDataSourceRequest with a date filter, the following is observed:
As you can see, the browser's UTC offset is discarded when constructing the query. This presents an issue when the backend server is running in a time zone that is different than the browser or is invariant. Internally toDataSourceRequest calls formatDateValue which calls toUTC. I propose adding an optional argument that allows us to skip this operation so that the offset can be kept as is, the reason being so that it can later be normalized to UTC without losing the information.
Calling toDataSourceRequest with the option should produce the following:
As demonstrated by the example of the current version and its screenshot, the title of the legend is black when using a dark theme:
Legend - Chart - Kendo UI for Angular (telerik.com)
The rest of the text is white which leads me to believe that this is a bug. This issue is not present when using a light theme.
The status bar is used to represent a summary of the aggregated values of the selected cell.
1. Start using the Kendo Tree View in Angular.
2. Load a large dataset for the Kendo Tree View, observe the time taken to render the Tree View.
3. The timing will increase if the dataset keeps on increasing.
4. Suggest some ways to reduce or optimize it.
In some calendar apps like Apple it's nice to extend appointments with a travel time (or preparation time).
Please extend Kendo Scheduler with such an event preparation-time and also a follow-up time, which looks like this:
Using the Editor component with Form Support, if I choose the style Heading 1 and type some letter.
I clean the value using only backspace key on the keyboard and the value of the form control is <h1></h1>.
This is reproductible on the demo : https://www.telerik.com/kendo-angular-ui/components/editor/forms/#toc-template-driven-forms
Expected result
Severity: Sev2
Environment (OS, Application, Versions):
OS: Windows11 (build 22631.3296)
Chrome Version 122.0.6261.129 (Official Build) (64-bit)
Chromium Edge Version 122.0.2365.80 (Official build) (64-bit)
AT (include version number):
NVDA Version 2023.3.4. (2023.3.4. 31265)
Jaws (Version 2024.2312.53)
Narrator (Version Win11)
Repro Steps:
1.Turn on NVDA screen reader.
2.Hit the Dropdowns Library - Overview | Kendo UI for Angular (telerik.com)
3.TAB till "AutoComplete" edit combo box and insert "C", suggestion list will expand.
4.Press down arrow key to navigate through expanded list.
5.Observe that NVDA is not announcing the available list items. 
Actual Results:
NVDA is not announcing the available suggestion list items of "Auto complete" combo box when we navigate with arrow keys.
Expected Results:
NVDA should announce the available suggestion list items of "Auto complete" combo box when we navigate with arrow keys.
9991592_NVDA_KendoExternal.mp4
VM4197:1 ERROR DOMException: Failed to execute 'setAttribute' on 'Element': 'aria-disabled]' is not a valid attribute name.
https://stackblitz.com/edit/angular-pxppfk-s4ix7b?file=tsconfig.json
Change target in tsconfig in this stackblitz to targer es2022 to recreate bug
Hi, Kendo team.
We have a small but annoying bug.
In the table filter for numeric column:
Is it any workaround for it?
Thank you.
Ekaterina.
Hi,
Many users of our apps have asked to add a "Clear" button to the Date Picker popup. For example, it could be placed next to the "Today" button. This would be something very useful and done without too much effort, as there is room in the popup and it doesn't involve any calculation.
Regards,
Augusto.
Hi,
I'd like to request a feature for programmatically dismissing notifications in Angular. This is a common feature for notification / toast component, but it is missing in Kendo UI for Angular.
Right now, once a closable notification is shown, there's no way to dismiss it programmatically, which can lead to clutter (see attached screenshot).
Here are the proposed features:
Programmatic Notification Dismissal:
Global Notification Limit:
These additions would greatly enhance the user experience by preventing notification clutter and providing better control for developers.
Thanks for considering this!
Best, Sergei.
When typing into the Angular Datepicker on iOS devices, the page scrolls unexpectedly after entering the first character of any date part (day, month, year). The scroll occurs on each subsequent character input (2nd, 3rd, etc.), making it difficult to use the input field.
Steps to Reproduce:
Expected Behaviour: The page should remain in place when typing, allowing smooth input without scrolling.
Observed Behaviour: The page scrolls up after entering the second character of any date part (day, month, or year) and continues to do so on each further input.
Reproduction: The issue was recreated using Kendo's own Datepicker example (with added spacing to demonstrate the scroll behaviour). https://stackblitz.com/edit/angular-v7j3ag
Affected Platforms:
Additional Notes:
I couldn’t find an existing bug report related to this issue, so I would appreciate it if you could confirm whether this has been reported or provide further guidance.
By default the grid pagination only works taking count of the actual records instead of (alternatively) taking in consideration the groups count.
It would be nice to have the possibility to choose between those 2 when using groupBy and process functions.
This pagination feature is already implemented in the Kendo Ui for Asp.Net Core, but it is not available in functions such as process, groupBy or (toDataSourceRequest/toDataSourceRequestString/toOdataString)
Here you can find the related documentation page for the Asp.Net implementation.
Right now the only possible way to achieve this behavior in combo with a KendoAngularGrid is to use the (toDataSourceRequest/toDataSourceRequestString), then into the controller you'll have to mutate the DataSourceRequest Object like following:
[HttpGet]
public async Task<IActionResult> GetData([DataSourceRequest] DataSourceRequest request, CancellationToken cancellationToken) {
var data = //... ;
request. Skip = (request.DataSourceRequest.Page - 1) * request.DataSourceRequest.PageSize;
request.Take = request.DataSourceRequest.PageSize;
request.IsExcelExportRequest = true; // without this the items property of the GroupResult type will be null
request.GroupPaging = true;
return Ok(await data.ToDataSourceResultAsync(request, cancellationToken);
}