In firefox, open the Kendo Radio Button documentation and slowly resize the window (https://www.telerik.com/kendo-angular-ui/components/inputs/radiobutton)

The radio button will kind of jiggle around and occasionally the white dot in the radio button will become off-center.

This also seems to happen in response to some material bouncy (cubic-bezier) animation transitions.

Kendo timeline range in the gantt can be miscalculated if children have start and end days earlier that their parent.

This happens to due oversight in TimelineBaseViewService.getRange function. Two variables startResult and endResult are calculated using only top-level entities from the supplied data hierarchy.

This stackblitz shows 2 cases.

1. The item is out of the bounds on the left due to an earlier start date than its parent's start date.
   
2. The item is rendered either as three dots or out of bounds on the right side (depends on the browser. Firefox tend to display three dots, Chrome clips the right side) due to end date being later than its parent's end date.
   

That's mostly visible on Day and Week timelines, however I believe can be reproduced on monthly and yearly views if the date spread is large enough.

Description

When you move the cursor to a new series item, the tooltip position does not move until you leave the chart area and re-enter. It changes the content based on where the cursor is pointing, but does not change the position.

Steps To Reproduce

1. Create a new Angular application
2. Add the Kendo UI Chart and paste the following code in the app.component.ts file:

import { Component } from '@angular/core';
import {KENDO_CHARTS} from "@progress/kendo-angular-charts";

@Component({
  selector: 'app-root',
  imports: [KENDO_CHARTS],
  template: `
    <kendo-chart>
      <kendo-chart-legend position="bottom"></kendo-chart-legend>
      <kendo-chart-series>
        <kendo-chart-series-item
          type="donut"
          [data]="data"
          field="value"
          categoryField="category"
          colorField="color"
          [holeSize]="60"
          [tooltip]="{
            visible: true,
            format: '{0:C0}'
          }"
          [highlight]="{ visible: true }"
        >
        </kendo-chart-series-item>
      </kendo-chart-series>
    </kendo-chart>
`,
})
export class App {
  public data = [
    { category: "Electronics", value: 245000, color: "#0058e9" },
    { category: "Clothing", value: 189000, color: "#37b400" },
    { category: "Home & Garden", value: 156000, color: "#f59c1a" },
    { category: "Sports", value: 134000, color: "#ff6358" },
    { category: "Books", value: 98000, color: "#8c43ff" },
    { category: "Toys", value: 78000, color: "#00acc1" },
  ];
}

3. Run the application

Screenshots or video

Actual Behavior

The Tooltip position only changes when you leave and reenter the Chart area. It does not change when you move the cursor from one series item to other, it updates the content displayed in the Tooltip though.

Expected Behavior

The Tooltip position should move with the cursor as seen in the screen recording below:

   I have tested kendo grid accessibility with AXE Dev tool. Found following errors that seems difficult to fix.

1)Certain ARIA roles must contain particular children

2)Scrollable region must have keyboard access

Any suggestion to fix these above-mentioned issues could be very helpful. Noticed these issues even exist in kendo grid demos published in kendo documentation. Check the link below

stack blitz link : https://stackblitz.com/edit/angular-uhjyd3x9?file=src%2Findex.html

When a tooltip of a dialog is shown and the dialog is closed, the tooltip is still present and is moved into the top left corner.

We use e.g. `kendo-dialog-titlebar` and the close button has a tooltip.

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

Hi,

if I change the [placeholder] input on a kendo-editor, the changes are not reflected.

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

Can you please take a look at it?

Best regards,
Michael

https://stackblitz.com/edit/angular-obj4gecf

If you click the first 2 cells in column "UnitPrice", the first one reports column 2 (which is correct), the second reports column 1.

I suspect rowSpan causes this, rows without rowSpan seem to work.

The DrawerAnimation interface isn't exposed in the index file.

DrawerItem, DrawerMode, and DrawerPosition are all exported but DrawerAnimation is missing.

The current FilterService does not handle nested composite filter descriptors, ignoring them and only processing individual filter descriptors. This limits functionality, especially for complex filtering scenarios. The request is to enhance FilterService to fully support and process nested composite filter descriptors.

Look at the notes for use cases.

It might be a formatting issue on my end

Hi ,

I want the kendoGridFocussable to apply the FocusableDirective on an anchor tag. This should allow the user to reach the anchor element using only the arrow keys without pressing Enter. (Example : Please, check out the following StackBlitz demo: https://stackblitz.com/edit/angular-rqqzam)

Regards,
Uzma

Hello,

When I try to delete all grouping manually by setting an empty group array, datas are disappearing. The grid datas are empty but reappears if I set grouping again. Also I could see data if I scroll down but I can't see any if I haven't enough lines to do so.

In attachment you could find a demo based on the "Collapse All with Grouping" tutorial.

First of all, thank you for providing the state management feature. For me it's one of the most important features of a grid component.

But unfortunately it fails to restore the columns state. This is because each time a grid component and it's columns are instantiated, new IDs are created for the columns. When loading state the columns are identified by their IDs.

When a column is persisted with e.g. id 'k-grid-column-1' and the grid will be destroyed and re-created, then the new column ID is not identical with the old one. Thus restoring the column's state will fail.

Please have a look to this StackBlitz example: https://stackblitz.com/edit/angular-vauqyshn?file=src%2Fapp%2Fapp.component.ts

A possible workaround is to save also the column's field property and later use it to re-map the saved id to the new id.

A better solution may be to extend the GridColumnComponent with something like a "PersistenceKey" property, which will be used for identifying a column. A directive may also work. Otherwise generating non transient unique ids for the grid columns will also work.

Best regards,
Holger

The directive `kendoGridColumnChooserTool` does not work correctly when having columns which are grouped. See this example: https://stackblitz.com/edit/angular-r9duqpcn?file=src%2Fapp%2Fapp.component.ts

1. It shows that 0 items are selected ("0 Selected items") - This is incorrect because all columns are selected by default. In the example above, I would expect it shows that 4 items are selected.
2. When unselecting an item in the list (popup), it does not actually hide any column.
3. When using directive `kendoGridToolbarTemplate` with `kendo-grid-column-chooser` component, it works as expected. I would expect that `kendoGridColumnChooserTool` directive would work (behave) exactly the same way.

import { Component } from '@angular/core';
import { FormsModule } from '@angular/forms';
import {
  KENDO_GRID,
  KENDO_GRID_EXCEL_EXPORT,
  KENDO_GRID_PDF_EXPORT,
} from '@progress/kendo-angular-grid';
import { KENDO_TOOLBAR } from '@progress/kendo-angular-toolbar';
import { KENDO_LABELS } from '@progress/kendo-angular-label';
import { KENDO_INPUTS } from '@progress/kendo-angular-inputs';
import { KENDO_BUTTONS } from '@progress/kendo-angular-buttons';
import { Product } from './model';
import { products } from './products';

@Component({
  selector: 'my-app',
  standalone: true,
  imports: [
    FormsModule,
    KENDO_GRID_EXCEL_EXPORT,
    KENDO_GRID_PDF_EXPORT,
    KENDO_GRID,
    KENDO_BUTTONS,
    KENDO_TOOLBAR,
    KENDO_LABELS,
    KENDO_INPUTS,
  ],
  template: `
    <kendo-grid
      [kendoGridBinding]="products"
      [pageSize]="5"
      [pageable]="true"
      [sortable]="{ mode: 'multiple' }"
      [style.width.%]="gridWidth"
    >
      <ng-template kendoGridToolbarTemplate position="bottom">
        <kendo-grid-column-chooser></kendo-grid-column-chooser>
      </ng-template>

      <kendo-toolbar overflow="scroll">
        <kendo-toolbar-button kendoGridColumnChooserTool></kendo-toolbar-button>
      </kendo-toolbar>

      <kendo-grid-column-group title="TestA">
      <kendo-grid-column
        field="ProductName"
        title="Product Name"
      ></kendo-grid-column>
      </kendo-grid-column-group>

      <kendo-grid-column-group title="TestB">
      <kendo-grid-column
        field="UnitPrice"
        filter="numeric"
        title="Price"
      ></kendo-grid-column>
      <kendo-grid-column
        field="Discontinued"
        filter="boolean"
        title="Discontinued"
      ></kendo-grid-column>
      <kendo-grid-column
        field="UnitsInStock"
        filter="numeric"
        title="Units In Stock"
      ></kendo-grid-column>
      </kendo-grid-column-group>
    </kendo-grid>
  `,
  styles: [
    `
      .example-info {
        background: rgba(83, 146, 228, 0.1);
        border-radius: 2px;
        margin: 10px auto 10px auto;
        padding: 15px;
        border-left: 4px solid #5392e4;
        font-size: 14px;
      }
    `,
  ],
})
export class AppComponent {
  public gridWidth: number = 100;
  public products: Product[] = products;
}

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 !

When setting the Checkbox component to disabled while the form is marked as touched, the k-invalid class is applied to the checkbox control.

That's because of the implementation of the isControlInvalid property:

public get isControlInvalid(): boolean {
    return this.control && this.control.touched && !this.control.valid;
}

According to the Angular source code:

    /**
     * A control is `valid` when its `status` is `VALID`.
     *
     * @see {@link AbstractControl.status}
     *
     * @returns True if the control has passed all of its validation tests,
     * false otherwise.
     */
    get valid(): boolean;

So valid() returns false when `status` is DISABLED.

The `isControlInvalid`property should better implemented like this:

public get isControlInvalid(): boolean {
    return this.control && this.control.touched && this.control.invalid;
}

Please check this Stackblitz: https://stackblitz.com/edit/angular-dznoe1xj?file=src%2Fapp%2Fapp.component.ts

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.

Hello Support,

There is a feature request for this, but I see this as a bug. The Agenda view in the scheduler is advertised to work perfectly on mobile, but I would expect to see the event column one way or another. Now you can only see timeslots, which is not that useful. Can you fix it by making the event column available, maybe as part of the time as text or some other solution.