When Toolbar component is configured to

1. Have spacer between two elements: Angular ToolBar Control Types - Kendo UI for Angular
2. AND it uses `overflow=menu` strategy: Angular ToolBar Responsive ToolBar - Kendo UI for Angular
3. AND when there is sufficient space, so the Toolbar is NOT overflowing. In other words, the visibility of the overflow button is set to hidden.
   

THEN the elements are not properly aligned with the right edge of the Toolbar component. This is because the overflow button still occupies the space as is the bahviour of the `visibility` style: visibility CSS property - CSS | MDN

• The visibility CSS property shows or hides an element without changing the layout of a document.

Minimal reproducible example:

import { Component } from '@angular/core';
import { KENDO_TOOLBAR } from '@progress/kendo-angular-toolbar';
import { FormsModule } from '@angular/forms';
import { KENDO_INPUTS } from '@progress/kendo-angular-inputs';
import { KENDO_LABELS } from '@progress/kendo-angular-label';

@Component({
  selector: 'my-app',
  imports: [FormsModule, KENDO_TOOLBAR, KENDO_INPUTS, KENDO_LABELS],
  template: `
    <kendo-label [for]="width" text="Set toolbar width"></kendo-label>
    <kendo-slider
      #width
      [(ngModel)]="toolbarWidth"
      style="width: 100%; display: block;"
      [showButtons]="false"
      [min]="0"
      [max]="100"
      [largeStep]="1"
      tickPlacement="none"
    ></kendo-slider>

    <kendo-toolbar overflow="menu" [style.width.%]="toolbarWidth">
      <kendo-toolbar-button text="My Kendo Angular Toolbar Button A" />
      
      <kendo-toolbar-spacer></kendo-toolbar-spacer>
      
      <kendo-toolbar-button text="My Kendo Angular Toolbar Button B" />
    </kendo-toolbar>
  `,
})
export class AppComponent {
  toolbarWidth = 100;
}

Expected behaviour: The overflow button does not occupy that space in the scenario described above.

• EITHER has `display: none` OR it is completely removed from the DOM when there is sufficient space.

You're docs say

Open the example in a new window to evaluate it with Axe Core or other accessibility tools.  for the Kendo angular grid

When i do that i see the attached error, which is the same issue i get in our product when running playwright axe

That suggests to me that it is not WCAG 2.2 compliant

Ensure elements with an ARIA role that require child roles contain them

.demo-frame.loaded.demo-module--wrap--718a6 > .demo-module--demoWrap--d1437 > .demo-module--explorerWrap--4bf1f.flex-grow-1 > .demo-module--demoBody--97eee > iframe #k-fbe44131-4768-4755-93c3-e321b714780e

<div role="grid" kendodragtargetcontainer="" kendodroptargetcontainer="" mode="manual" class="k-grid-aria-root" id="k-fbe44131-4768-4755-93c3-e321b714780e" aria-label="Data table" aria-rowcount="62" aria-colcount="5">

<div tabindex="-1" class="k-grid-content k-virtual-content">
 
 

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

I'd like to report that my issue linked in Duplicated item was not fixed: 

Closed bug: https://feedback.telerik.com/kendo-angular-ui/1484071-scheduler-event-editor-recurrence-editor

My bug marked as duplicate: https://feedback.telerik.com/kendo-angular-ui/1657303-scheduler-some-events-are-incorrectly-duplicated-despite-the-rules-written-on-them

It can still be reproduced in new version 17.3.12 

https://stackblitz.com/edit/angular-pusn73-en4gpcjt?file=src%2Fapp%2Fapp.component.ts

The event with recurreneRule that suggests that this event appears on each Tuesday till 20201014 is visible on Wednesday 14th.

Currently, it is not possible to enter a date that falls exactly on a Daylight Saving time.

Check the following example where it is not possible to enter 3 for the hours' section (it is also not possible to select 3 from the TimePicker popup):

https://stackblitz.com/edit/angular-nstdolh5-xfiws9nr

That behavior is expected as there is no such time in the Bulgarian time zone. Daylight saving time begins on 30 March 2025 03:00 when the time is moved 1 hour forward.

The demonstrated undesired behavior for the specific date will be reproducible only if the example is opened in the specified time zone. But the same behavior is valid for any other date that falls on Daylight Saving time in other time zones.

We should decide on what the expected behavior is for such cases. For example not allowing entering the value, displaying an error, auto-switching to the real hour (4 AM), etc.

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.

Hello,

Please repeat the following steps to reproduce this issue:

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

It seems that whenever a task crosses the date where the daylight saving time switch appears everything on the gantt's week view gets shifted by 1 hour.

This stackblitz shows 2 Gantts. The first one has correct positioning, the second one appears to be bugged.

In this picture, you can see that in the 1st Gantt `Item 1` is slightly shifted to the right and covers Thursday and Friday. That's because its date is specified in UTC as `2025-04-03T00:00:00.000Z` which, for me in the UK, will result in `01:00:00.000`.
However, in the second Gantt `Item 1` now fully covers Thursday and doesn't extend to Friday even though the start and end dates are the same as in the first Gantt.

You might get slightly different positioning based on your time zone. The description is written based on the UK time zone.

It also affects drag-and-drop marquee. If you try to drag the right side of item 1, you'll see that it will show Saturday even before it starts covering Saturday.

Expected behaviour: Item 1 has to be positioned identically on both timelines

Currently tooltip can be rendered outside of the gantt component if item on the timeline is long enough to be outside of the timeline viewport.

Adjusting [taskTooltipOptions] doesn't help as tooltip will still be outside of the timeline viewport.

Steps to reproduce.

1. Open Stackblitz
2. Scroll to Sat 19/04
3. Hover mouse of Sat 19/04 slot

The tooltip data isn't loaded properly when the mouse lands on the item due to the horizontal scroll rather than moving moues manually. This behaviour is mostly noticed on touchpads due to gestures.

See stackblitz.

Steps to reproduce

1. Place the mouse pointer before any item on the gantt
2. Scroll to the right or left without moving the mouse so the pointer stops on the item

It's important not to move the mouse, as soon as any action like movement or click happens the tooltip loads the data.

See the attached video.

We are exporting an Excel from a treelist -> there are merged cells, and the table has lots of rows (~20k).

It's taking forever (it's unusable) and the reason is that there is an O(N^2) bug in the toXML function: each row adds a merged cell range, and the mergedCells array is scanned linearly for every new row.

I was able to fix this by adding a mergedCells hash (I would be happy to create a pull request).

Also, as a related issue, it would be nice to be able to change the compression level on the generated zip file, because the default again takes forever for large enough files.

When applying font-size, the bullet list dots aren't affected by yhe changes as the MS Word behave:

MS Word

https://stackblitz.com/edit/angular-e53ira?file=src/app/app.component.ts

If the popup is off-screen, it is simply cut off, unlike vertical which flips it to the other side.