I have installed kendo-angular-layout package and after running the command npm start Im receiving the errors represented in the pictures. 

Im not sure how to fix this?

Im not sure how to check my Kendo package version as well /

I have being trying to implement the multiple row selection function but am unable to get multiple rows selected at once, even though I have multiple selected mode enabled,Is it possible to archieve this in Kendo ui grid in Angular?

Please see my function bellow. event=1 row always even though I select more one row.

Select all checkbox provided in tree list module is not working as expected. Below are the detailed step to reproduce

To Reproduce

Scenario 1 :

1. Checked on select all checkbox
2. Unchecked any of the row, the select all checkbox still checked.

Scenario 2 with pagination:

1. Checked on select all checkbox
2. Move to next page
3. Select all checkbox is checked, but the rows is not selected

Scenario 3:

1. Checked on select all checkbox
2. Expand the parent node, the child node is not checked

Expected behavior
Scenario 1:
The select all checkbox should be unchecked. Same as what provided in Grid module
Scenario 2:
The select all checkbox should be unchecked
Scenario 3:
The child node need to be checked

Autosize on treelist with locked columns does not work

When the width of the grid exceeds the column lengths, you would expect autosize to expand and fill the rest of the space evenly.

https://stackblitz.com/edit/angular-7rxada-84kfzy?file=src/app/app.component.ts

Similar to https://github.com/telerik/kendo-angular/issues/3248

The kendo scheduler when opened in the mobile view the events tittle inside the month view texts are broken and hide in responsive design.

The user did not see the full event tittle texts in month view in responsive Design. 

please refer below  attachments here.

Hi,

We would like to use the MultiSelect-Control in combination with kendoDropDownFilter and autoClose set to false. 

Now when we start typing and hit enter to select a value the filtering text is not cleared and the control is a faulty state.

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

There seems to be a styling bug in the Kendo theme for Bootstrap.

Default Bootstrap buttons has this strange shadow or border issue

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

1. If a detail row is expanded, the entire virtual scroll fails - showing whitespace/not loading new data once you scroll enough to trigger pagination/new dataset load. It remains broken even after collapsing the details row.
2. Scroll down and filter - you see white area. You need to scroll until it triggers data load to fix it.

    .k-coloreditor-header {
        padding: $coloreditor-header-padding-y $coloreditor-header-padding-x 0;
    }

The style rule uses the two variables - with x and y respectively, yet has a hardcoded 0px value as a third parameter.

This causes x to only apply top padding, which is misleading.

Can i reorder tabs using drag and drop in angular ?

How i need to close kendo sortable item in angular? is there any event for that?

Hi,

This documentation Stackblitz demo is broken (see screenshot below for details).

Essentially the most basic GridComponent when ngIf'd in and out will not be collected -- apparently because of orientation change / resize change listeners not being appropriately removed.

Steps to Reproduce

Click the TOGGLE TABLE button to hide the table

Click the TOGGLE TABLE button to show the table

repeat several times

Take a memory snapshot

There will be HTMLTableRowElement items that grow each iteration of toggling the table.

The HTMLTableRowElements retention shows that they eventually lead to a resize listener, or an orientation change listener.

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.

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

if editor recive a value like '<span class="platzhalter">Empfaenger_Debitor</span>'

by rendering console show this error

When you implement the activeViewDateChange and scroll through the calendar, the event is properly triggered.

But when you navigate through the calendar using the month navigation, this event is only triggered(multiple times) when you skip at least 1 month

Sample code - Kendo event sample code: https://www.telerik.com/kendo-angular-ui/components/dateinputs/calendar/#toc-events

Scenario:

Current month: Januari

Next month: Februari

Expectation: (activeDateChange: 1-2-2020)

Result: - / not triggered

Current month: Januari

Next month: June

Expectation: (activeDateChange: 1-6-2020)

Result: (activeDateChange - 1-5-2020), (activeDateChange - 1-6-2020) / event triggered twice

Not sure if this is a bug in Angular CLI, Karma, or Kendo. I wrote up a bug for Angular CLI for this as well: https://github.com/angular/angular-cli/issues/20449

Issue only tested on Windows 10 x64 with Chrome 89 installed.

1. Create new application:
   ng new <app-name> --strict=true --style=scss --routing=true
2. Install @progress/kendo-theme-default
npm install @progress/kendo-theme-default --save
3. Open styles.scss, add the following line:
   @import "~@progress/kendo-theme-default/scss/all";
4. Open karma.conf.js and change the following properties:

    autoWatch: false
    browsers: ['ChromeHeadlessCI'],
    customLaunchers: {
      ChromeHeadlessCI: {
        base: 'ChromeHeadless',
        flags: ['--no-sandbox']
      }
    },
   singleRun: true

5. Run ng test

After 2+ minutes, warning in console shows: WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.
Then, NFO [launcher]: Trying to start ChromeHeadless again (1/2).
The second time launches without issue.

If you remove the line from styles.scss and repeat ng test, the problem is not visible.

Alternatively, check out this repo and run ng test :https://github.com/acohenOT/unit-testing

Warning indicated below:

Karma v6.1.2 server started at http://localhost:9876/
05 04 2021 12:20:05.510:INFO [launcher]: Launching browsers ChromeHeadlessCI with concurrency unlimited
05 04 2021 12:20:05.536:INFO [launcher]: Starting browser ChromeHeadless
- Generating browser application bundles (phase: building)...05 04 2021 12:22:32.075:WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.
/ Generating browser application bundles (phase: building)...05 04 2021 12:22:32.986:INFO [launcher]: Trying to start ChromeHeadless again (1/2).
√ Browser application bundle generation complete.
05 04 2021 12:22:39.009:INFO [Chrome Headless 89.0.4389.114 (Windows 10)]: Connected on socket 6ClQVkn2c_tOxxhlAAAB with id 89607273
Chrome Headless 89.0.4389.114 (Windows 10): Executed 3 of 3 SUCCESS (0.305 secs / 0.217 secs)
TOTAL: 3 SUCCESS

While the grid is initially loading data, the "No records available." message is confusing and provides no useful information.

Expected behavior - when the grid is initially loading, don't display the message as the rows/data might very well appear

To reproduce basically just go to the grid demo page (refresh if needed) and pay attention to the grid loading: https://www.telerik.com/kendo-angular-ui/components/grid/data-binding/

Example in our project - intuitively you'd think that the grid has no records until you see the loader; in any case, the message looks out of place: