The page numbers and total items within a pager do not appear to respect the currently loaded i18n locale. For example, there's no comma in the thousands place for the en locale. What makes me believe this is a bug is that the page input which can appear DOES have i18n applied to it so the discrepancy is clearly visible between the two.

As there's no demo with such large page numbers I've created an example as well as a screenshot:
B187rdik (forked) - StackBlitz

When dateinput format is "d/M/y" and "allowCaretMode" is enabled, users are unable to enter valid dates. Tested with dateinput and datepicker components.

Steps to reproduce

1. Setup a kendo-dateinput component with "allowCaretMode" set to "true" and the "format" set to "d/M/y" (see stackblitz below).
2. Enter a valid single-digit day and valid single-digit month into the input
3. Try typing a year
4. Observe that only one character of the year can be entered and the input locks up, preventing the user from completing a valid date.

Stackblitz example

https://angular-x4rvxqyp-qfq5b7mj.stackblitz.io

Expected Behaviour:

The user should be able to enter a full year after typing a valid single-digit day and month.

Observed Behaviour:

After entering a single-digit day and month, the input locks up, preventing the user from typing more than one character for the year. This prevents users from entering valid dates, making the input unusable in this scenario.

I couldn’t find an existing bug report related to this issue. Could you confirm whether this has already been reported or provide guidance on a potential fix or workaround?

Thanks

 

 

 

I’d like to request two enhancements to the DateTimePicker:

Custom Timezone (e.g., UTC): Allow the ability to set a custom timezone, overriding the system clock for consistent time handling (e.g., UTC).

Timezone-Aware "Now" Button: Enable the "Now" button to respect the selected timezone. For example, if the timezone is set to UTC and the current UTC time is 12:00:00, clicking "Now" should display 12:00:00 instead of the local time.

These features would improve flexibility for timezone-specific applications and ensure consistency in timestamp-based operations. Thank you for considering this request!

On the latest version, horizontal scroll is not visible for multi resources. if have more 5 resources also, the table is shrinking but scroll is not enabled. 

./node_modules/@progress/kendo-angular-layout/fesm2022/progress-kendo-angular-layout.mjs:19:0-75 - Error: Module not found: Error: Can't resolve '@progress/kendo-angular-progressbar' in 'C:\LiveMRIProjects\MRI.AgoraInsightsAnywhere-Angular\node_modules\@progress\kendo-angular-layout\fesm2022'

./node_modules/@progress/kendo-angular-layout/fesm2022/progress-kendo-angular-layout.mjs:22:0-56 - Error: Module not found: Error: Can't resolve '@progress/kendo-angular-intl' in 'C:\LiveMRIProjects\MRI.AgoraInsightsAnywhere-Angular\node_modules\@progress\kendo-angular-layout\fesm2022'

 

this is the error is coming

when we add kendo thing into module.ts file

Issue 1: Flickering or Not Opening of Dropdown

• Steps to Reproduce:
  1. Click on the color picker.
  2. Click on any dropdown.
  3. Observe the behavior of the dropdown.

Issue 2: Clicking on Color Picker and Dropdowns (Dropdown not closing)

• Steps to Reproduce:
  1. Click on the color picker.
  2. Click on any dropdown.
  3. Repeat this with all dropdowns to get above screenshot.

If the pane is scrolled, the dark highlight shown when grabbing the splitter is misaligned like this:

Stackblitz repro can be found here

I am using below piece of code inside <kendo-grid>. Here, I am using a dropdown and kendo excel export button inside toolbar. dropdown is in left and button is right aligned. Earlier, it was working till Kendo 18. When I upgraded to kendo 19, it stopped working. 

Root Cause is kendo-dropdownlist contains an array button. When we click on button to expand dropdown, excel export button gets the focus and dropdown loses focus. When we click on dropdown button, 'k-focus' class is applied on 'excel-export'. Because of this, dropdown is not working. 

 

Code:

<ng-template kendoGridToolbarTemplate>

        <div class="toolbar-container" style="display: flex; align-items: center; gap: 16px; width: 100%;">

            <!-- Dropdown Wrapper -->

            <div style="flex-shrink: 0;">

                <kendo-dropdownlist [data]="data"

                    [(ngModel)]="someField" [valuePrimitive]="true" (valueChange)="perform()"

                    [popupSettings]="{ appendTo: 'component' }" style="width: 175px;">

                </kendo-dropdownlist>

            </div>

 

            <!-- Spacer to push button to right -->

            <div style="flex-grow: 1;"></div>

 

            <!-- Excel Export Button -->

            <div style="flex-shrink: 0;">

                <button type="button" kendoGridExcelCommand>Export</button>

            </div>

        </div>

    </ng-template>

Hello,

I tried to implement this new feature : https://www.telerik.com/kendo-angular-ui/components/grid/scroll-modes/virtual#controlling-the-expanded-state-of-all-root-level-groups

You can see in the demo that if you remove all grouping, the content is now limited to 50 lines instead of displaying the whole 1000.

I found a workaround by expanding all before removing the grouping but it is not very user friendly.

If you can patch it ASAP that would be great. 

And thank you to finally have pushed this long awaited feature !

We are using the dialog service by dynamically importing and providing standalone components. The problem that we are experiencing is that seems those components aren't created in any injection context. So there is really no way if we want to reuse some shared service that is provided in the component that opens the dialog. Would be great if in the options that are passed to the open method of the dialog service we could also specify an injector, which will then be used when creating the instance of the dynamic component. This way we can pass the injector of the calling page which should provide any shared service that are provided in the calling page.