Pending Review
Last Updated: 09 Oct 2019 06:51 by ADMIN
In TabStrip control with angular 7: when moving to another tab and hitting ngAfterViewInit() on that tab's component -> previous tab's component still exists - showing 2 components together.
Pending Review
Last Updated: 27 Sep 2019 14:40 by ADMIN

Steps to reproduce:

1. Run application and open the schedule component

2. Start drag the element on schedule to new place and drop it.

After that whole schedule component will blink(in Chrome, for example, all OK).

Pending Review
Last Updated: 29 May 2019 14:03 by ADMIN
Created by: William
Comments: 1
Category: Kendo UI for Angular 2+
Type: Bug Report
0

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.

Under Review
Last Updated: 29 Mar 2019 06:53 by ADMIN

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

 


Declined
Last Updated: 28 Mar 2019 13:28 by ADMIN
When the grid component is set to virtual scroll mode, the popup component cannot be correctly positioned to its anchor in the grid cell.
Completed
Last Updated: 28 Mar 2019 13:19 by ADMIN
Created by: Kendo UI
Comments: 1
Category: Kendo UI for Angular 2+
Type: Bug Report
0

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

Completed
Last Updated: 28 Mar 2019 13:14 by ADMIN
Created by: Matjaž
Comments: 1
Category: Kendo UI for Angular 2+
Type: Bug Report
1

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).

Completed
Last Updated: 28 Mar 2019 13:12 by ADMIN
Created by: Richard
Comments: 1
Category: Kendo UI for Angular 2+
Type: Bug Report
0
Completed
Last Updated: 28 Mar 2019 13:10 by ADMIN
Created by: Paolo
Comments: 2
Category: Kendo UI for Angular 2+
Type: Bug Report
0

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.

 

 

Declined
Last Updated: 20 Mar 2019 12:32 by ADMIN
Created by: Mark
Comments: 5
Category: Kendo UI for Angular 2+
Type: Bug Report
0

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 = ...
}