Dear Support Team,

Although I changed my locate to 'fa-IR', the kendo UI date picker did not change to Hijri or Jalali Calendar and it just translated the text of the gregorian calendar!

Is this a bug? or I should do something to use the Persian calendar?

Best regards

HI

When i input a value with 11111111111111111 on  kendo-numerictextbox and  lost focus (blur) event the value is always change to 11111111111111112 .Any solution  to prevent this issue ?.

https://stackblitz.com/run/?file=app%2Fapp.component.ts

Hello, I am trying to use the table-related toolbar tools in my editor. I am getting the compiler.js:2175 Uncaught Error: Template parse errors:
'kendo-editor-insert-table-button' is not a known element:
1. If 'kendo-editor-insert-table-button' is an Angular component, then verify that it is part of this module.
2. If 'kendo-editor-insert-table-button' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message. ("               <!-- Kendo Built-In Toolbar tools not working correctly -->.

I have not had an issue with any other toolbar tools.

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));
    }
}

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