When the chart is configured to use the selection zoom. One must press the Shift-Key and select an area inside the chart to zoom.

I the chart shows tooltips, in most cases the tooltip pops up under the cursor and it is not possible to select an area.

The tooltip shoud be disabled, when the shift-key (or the configured key) is pressed inside the chart area.

Hello

Currently the datePicker and probably other controls that implement the rangeValidation property do not listen to changes on the rangeValidation input.

This is preventing whether range validation is enabled based on other form input changes during user interaction with the form.

Can this be changed so it listens on ngChanges?

I found an issue with the kendo-window component. Sometimes when you have a window component with an embed element inside it and you start dragging the window and then click inside the embed element (In the example a PDF viewer), after that you click again in the window’s title bar the window is stuck in the dragging state and it keeps following the mouse pointer even when you already release the mouse button.

It is an odd behavior and we need to know how to stop this, but without disabling the dragging functionality for the kendo-windo.

Here is the repro-case in stackblitz: https://stackblitz.com/edit/angular-jqjemx

Perhaps you need to try clicking over several times in order to reproduce this behavior.

The problem is that in our application the pointer position remains inside the embed element and we can’t click the title-bar again to release the dragging mode.

When using the "checkBy" attribute to configure the data field for the key definition, then the indeterminate state of parent nodes is broken.

To reproduce the issue have a look to this StackBlitz: https://stackblitz.com/edit/angular-okpokx

In Version 74.0.3729.108 (official Build) (64-Bit) of chrome, a defined grid with no predefined style property does not scroll properly. 

There is a live-demo on Stackblitz at https://stackblitz.com/edit/angular-b38r7s-jzsgty

This is a fork of the demo example from the kendo-angular-ui documentation available at

https://www.telerik.com/kendo-angular-ui/components/grid/scroll-modes/virtual/#

In the example, the scrollable grid was defined with a height property. This does not feet to our requirements, as we need a grid component that should flex according to the outside or parent container. 

This problem occured after the update of chrome browser from 73.0.XXX to the version 74.0.3729.108

The problem is fixed when we defined a grid with a height property like [style.height.%] = “100” but according to the documentation the grid should flex automatically without this property. 

Use IE11:

1. Try to use the grids column menu for filtering

2. Click the column icon => popdown menu opens

3. Click the filter oder column icon inside the menu => nothing happens

I can't even open up your docs using IE11, it just loads forever:
https://www.telerik.com/kendo-angular-ui/components/grid/columns/menu/

In the example below "X-Small" is initially the selected item in the dropdown.  Once you click the "Sort" button and sort the array, "2X-Large" becomes the highlighted item in the dropdown but "X-Small" is displayed.  I would expect that "X-Small" would be highlighted.  After opening and closing the dropdown "2x-Large" becomes the selected item even if you don't select it.  The same behavior does not happen with a simple select dropdown.

import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'my-app',
  template: `
  <form>
    <div>
      <p>T-shirt size:</p>
      <kendo-dropdownlist [data]="listItems" [(ngModel)]="selectedShirt" name="shirtsize">
      </kendo-dropdownlist>
    </div>
    <br/>
    <div>
    <select [(ngModel)]="selectedShirt" name="shirtsize2">
      <option *ngFor="let d of listItems">{{d}}</option>
    </select>
    </div>
    <br/>
    <button (click)="sortArray()">Sort</button>
  </form>
  `
})
export class AppComponent implements OnInit {
    public listItems: Array<string> = ["X-Small", "Small", "Medium", "Large", "X-Large", "2X-Large"];
    public selectedShirt: string;
    ngOnInit(){
      this.selectedShirt = this.listItems[0];
    }

    sortArray(){
      this.listItems.sort((a, b) => a.localeCompare(b));
    }
}

Hi,

We encountered a problem when using kendo-sortable component in IE11. If we use this component anywhere on the page, all input fields on the page become unclickable. It seems to happen in the last version of this control (maybe because of a global click event listener? )

Hope you can help with this issue.

You can check out the following Stackblitz example which is based on your basic usage example: https://angular-t7vi5k.stackblitz.io/

Thanks in advance and happy holidays,

Shai Aharoni

When both virtual scrolling and grouping are enabled via the kendoGridGroupBinding directive, and the Grid is navigable, focus is trapped in the header row when down or up arrow is pressed:

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

1. Focus any content cell

2. Press up/down - focus goes to the header cell of the respective column and is trapped in the header row

On a feedback portal search and paging is not working.

Open feedback portal and enter search criteria with more then five item. example

When you want to view result for second page, search is not preserved (it is empty).

The example does not work:

https://www.telerik.com/kendo-angular-ui/components/tooltip/how-to/show-grid-cells-content/

I want to filter the scheduler data but I had to add the OwnerId property to the node package interface in order to be able to do so... yet the sample data provided in the examples does include the ownerId, so im guessing all that needs to be done is to add it to the interface.

Hi,

When opening a dialog with DialogService from an Observable (e.g. in order to initialize dialog with data from a http request) and ChangeDetectionStrategy.OnPush, the dialog is messed up. With ChangeDetectionStrategy.Default everything works fine.

For reproduction have a look to this StackBlitz: https://angular-9vmvyv.stackblitz.io

Regards,
Holger

The manner in which the Kendo Grid handles multiple column sorting is unusual and therefore not what a user would expect.

I believe that people expect that the column they click on to always be the primary sort column.  In the Kendo grid, (when in multi-column mode) this is not the case.

If I click on the "Unit Price" column header, and then on "Product Name", nothing happens.  Instead, clicking on "Unit Price" a second time sorts the table by "Product Name".  This is not natural. 

Instead, this should simply behave like a non-destructive sort.  If I click on "Unit Price" and it sorts by that.  Then, clicking on "Product Name" should sort everything by Product Name and, if the names are the same, the items would be sub-sorted by the previously selected column: "Unit Price"

I would further ask that the only column that shows the arrow be the primary sort column.  Users want to see what the primary sort column is, and not be confused by the other columns, which they will assume are sorted in a reasonable way.  The indices help, but I still think that a single arrow denoting the primary sort column would be preferred.

https://www.telerik.com/kendo-angular-ui/components/grid/sorting/

To be backwards compatible, maybe introduce a 'natural' sort mode which would behave in this manner, since I really believe that this is what a user expect.

As a workaround, we put the grid in 'single' mode, and then when the sort changes, we do the following.  I limit the number of SortDescriptors to 3 as a compromise between sorting the columns in a reasonable way and yet prevent there from being too many arrows

public autoSortChange(sorts: SortDescriptor[]) {
   let singleSortKey = sorts[0];
   let newSort: SortDescriptor[] = [];
   newSort[0] = singleSortKey;
   this.internalSortDescriptors = this.internalSortDescriptors.filter(des => des.field !== singleSortKey.field)

   newSort = sorts.concat(this.internalSortDescriptors)

   this.internalSortDescriptors = Array.from(newSort);
   if (this.internalSortDescriptors.length > 2) {
    this.internalSortDescriptors.length = 2;
   }
   this.gridState.sort = newSort;
   this.gridData = ...
}

As you can see from the image below the tab strip tabs can keep getting added and they do not care where the parent DIV or any other container ends. It would be appropriate for them to allow for scrolling if it goes outside the width of its container.

This is the way it is handled in jQuery

https://demos.telerik.com/kendo-ui/tabstrip/scrollable-tabs