https://stackblitz.com/edit/angular-sdmdrbjt-5yunmeo2

Currently, in Kendo UI for Angular Charts, when using multiple axes of the same orientation (e.g., two Y axes), only the major grid lines of the first axis are displayed. The grid lines of the second axis (Y2) are ignored, even if enabled in the configuration. This limits the readability of multi-axis charts, as it is not possible to visually distinguish the graduations of each axis.

Add an option (for example, showGridLinesOnAllAxes: true) that would allow displaying major grid lines on all axes, not just the primary one.

The Kendo team suggests using plot bands to simulate the grid lines of the second axis, but this solution is less convenient and requires manual configuration.

Below is a screenshot of what it might look like; the first graph shows what is currently possible, and the second shows what would be possible if this feature were added.

We found a bug in our application on tablet portrait mode when we want to select a date from the filter menu inbuilt feature of Kendo grid. 
When the user wants to select a date, the filter closes up and the user is not able to select any date from the calendar.

The issue is happening on tablet device in portrait mode and we found out that it's happening on your documentation too. To reproduce the issue, please go to the "Angular Grid Filter Menu" in your documentation:
https://www.telerik.com/kendo-angular-ui/components/grid/filtering/filter-menu/

Please open the dev tools and set the browser on any tablet portrait size or use Galaxy Tab S4.
In your first example (Angular Grid Filter Menu), please click on the "Date" filter in the grid. When the popup opens up, please click on the calendar icon 
of the date input field. 
When the calendar shows up, try to select any date. You'll see that the filter closes up and the user is not able to select any date. Demo video attached for reference.
Please fix this bug as we support Samsung Galaxy tablet devices and we're using this feature in our project.  

Currently, the (X) close button is always shown and visible. In other words, it is not possible to configure the dialog component to NOT display this icon button. It is actually not just about the icon button, but also the ESC shortcut. It should not be possible to close the dialog when the input is set.

Feature request: Add an input `closable` for the Dialog Component ('kendo-dialog') to be able to turn off the closable behaviour. Example:

```html

  <kendo-dialog [closable]="false"></kendo-dialog>

```

The "closable" is `true` by default, ensuring that it is backwards compatible.

 

Use case: A certain dialog is presented to the user and user must NOT be able to close/ignore the dialog. The user is thus forced to resolve the instructions presented in the dialog and resolve it the intended way.

Please provide a way to disable the months or years when displaying months or years in the Calendar. The disabledDates callback function could be evaluated for these views.

Thank you

Hi,

if I use both the features locked columns and sticky rows, the sticky rows do not stick in the locked columns.

For me it would be logical if they would stick there too (now the UI looks inconsistent):

Reproduction (forked from your example): https://stackblitz.com/edit/angular-wak7v99i 

Can you please take a look at it?

Best regards,
Michael

Description of the Requirement (Use Case) In our enterprise Angular application, we require the UI to run on a synchronized "Customer Time" rather than the physical machine's local OS time. We calculate a monotonic time drift against our server's timestamp to ensure absolute accuracy for scheduling, regardless of the user's laptop clock settings or local timezone.

Currently, we need the <kendo-scheduler> (specifically the Current Time Marker, ongoing event highlighting, and the "Today" navigation action) to respect this synchronized server time.

The Current Limitation Kendo UI Scheduler and Date components internally rely on the global window.Date object (via new Date() and Date.now()) to determine the "current" time. While Kendo provides a [timezone] input to shift event displays, there is no native API to provide a custom clock provider for the "Now" state. The Current Time Marker will always strictly render the user's physical OS time.

Currently the kengoMultiSelectSummaryTag only supports a number as its input, which enables switching to summary mode if the number of selected items is greater than the specified value.

It would be nice to add an option for dynamic mode which will be based on the available space for the control and will automatically switch to summary mode if there is not enough  space for displaying all the items.

See the screenshots to illustrate how it might look like.

Thanks,

Shai.

 

Hi Team,

Please add a feature to add an option that allows choosing between the Dialog and the Window component when using the `View source` tool. so that view source window can be resized.

Provide an eventSpacing option similar to jQuery to specify the distance between events.

https://www.telerik.com/kendo-jquery-ui/documentation/api/javascript/ui/scheduler/configuration/views.eventspacing

 

We are using the Kendo UI for Angular Gantt and would like to request built‑in support for deleting task dependencies directly within the Gantt chart.

Right now, dependencies (the arrows connecting tasks) can be created, but not removed through the UI. For our use case, it would be very helpful if users could manage dependencies more intuitively.

What We’d Like to See

Any of the following options would work well:

• Clicking a dependency line opens a simple confirmation dialog asking whether the dependency should be deleted.
• Selecting a dependency and pressing the Delete key removes it.
• Selecting the dependency handle/bubble (the same one used to drag and create dependencies) and pressing Delete.

Hi,

Currently, the 'More Events' button is not accessible through keyboard navigation, and it would be helpful if it could be made accessible.

In OData 4.01 the 'in' operator was introduced (https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_In). Can this also be implemented in the toODataString function?

Currently, the user cannot select the time cells, and it would be a nice improvement if it were possible to select the time cells and highlight both the time and event cells upon focusing on the cell. The functionality should be similar to how jQuery does it in their Scheduler Agenda view.

https://demos.telerik.com/kendo-ui/scheduler/keyboard-navigation

 

Hi Telerik,

It would be great if we can add Select All functionality as a built-in feature of the MultiSelect component. It is especially useful when working with checkboxes, e.g., https://www.telerik.com/kendo-angular-ui/components/dropdowns/multiselect/templates/#toc-rendering-item-checkboxes.

The cols and rows property in the GridLayout can only be an array of strings and/or numbers. Please add the ability to use a min function something like: [cols]="[145, min(145, auto)]" or [cols]="[145, min(145, 12%)]"

Hi,

It will be very useful if an Azure layer is provided to the Map component, similar to the Kendo UI for the jQuery map widget:

https://demos.telerik.com/kendo-ui/map/azure 

 

Currently, if you use Shift to select rows 3 through 6, then clear the selectedKeys array, and later perform a new Shift-click selection on row 9, the selection includes rows 6 through 9.

Add a method to reset the selection state so the next Shift-click starts from the default rangeSelectionStartRow instead of the previous selection.

Introducing a compact mode in the component would help prevent unused empty space. There is an existing Kendo jQuery feature request with a significant number of votes.

Dynamic grid status content does not announce updates to screen readers during filtering or pagination.
For example, the status message “1 – 4 of 4 items” updates visually but is not announced to assistive technology users.
As a result, screen reader users do not know when filtered or paged results change.

This can be improved to read out how many items are left on the page for the user to navigate them, as in some cases, there might be none. 

The default item approach is not suitable for some of our UX use cases.