Here is a simple example:

HTML:

<kendo-listview
  [height]="400"
  [data]="notes$ | async"
  class="k-d-flex-overflow-auto"
  (scrollBottom)="loadMore()">
  <ng-template kendoListViewHeaderTemplate>
    <span title>Reminders</span>
  </ng-template>
  <ng-template kendoListViewItemTemplate let-dataItem="dataItem">
    <app-message-note [note]="dataItem"></app-message-note>
  </ng-template>
</kendo-listview>

TS: 

@Component({
  selector: 'app-message-list',
  templateUrl: `./message-list.component.html`,
  styles: [
    `
      .k-d-flex-overflow-auto {
        display: flex;
        flex-direction: column;
        flex-wrap: nowrap;
        overflow: auto;
      }
    `,
  ],
})
export class MessageListComponent implements OnInit {
  notes$: Observable<NoteDto[]>;

  constructor(private replyService: ReplyNoteService) {}

  ngOnInit(): void {
    this.notes$ = this.replyService.getUserNotesList();
  }

  loadMore() {
    console.log('loading...');
  }
}

Without these styles scroll is not visible.

Current behavior: scroll to the bottom, nothing happens.

Expected behavior: scroll to the bottom "loading..." will be logged to the browser console.

Currently angular will fail builds due to type check if kendo-timepicker value is null/undefined.

It requires it to always be a date - making it impossible to have initially empty values or to even reset the selection/value and show a placeholder.

Even the documentation for placeholder says:

Specifies the hint the TimePicker displays when its value is `null`.

private _value: Date = null;
@Input() public set value(value: Date)

But the input does not allow this. Even the property is defined in a way that would fail type checks in any newer angular project (strict mode is the default).

The only workaround currently is to  disable type check with $any()

For Angular Kendo Scheduler, if the Work week view is selected (default Mon-Fri), and Sunday is selected on the mini calendar to select the date to display - the previous week will be displayed. This is confusing, as simply toggling to Week view will then display the different, current week.

https://www.telerik.com/kendo-angular-ui/components/scheduler/views/day-week/

Expected behaviour: current week on mini calendar corresponds to the current week displayed regardless of whether full week or work week view is selected

Actual behaviour: selecting any day up until the desired "work week's start" (even if it's customized to start on e.g. Tuesday - and selecting Monday) will show previous week; switching then to full week view switches the week displayed to the one selected on mini calendar

------

Curiously, this does not happen for Kendo scheduler for JQuery (https://demos.telerik.com/kendo-ui/scheduler/index):

when someone clicks on a date in the middle of the component, it will scroll the component instead of selecting the date.

This occurs in chrome and edge. In firefox this issue is not observed.

Steps:

1. Open a datepicker (https://www.telerik.com/kendo-angular-ui/components/dateinputs/datepicker/)
2. Hover over tuesday (bootstrap theme), between tuesday and wednesday in default theme.
3. Click on the date.
4. The component scrolls instead of selecting the date.

The cursor also changes from pointer to default. It seems another component is on top of the tuesday column.

After updating to Angular version 17.3.0 the TabStripComponen throws errors:

• Error: Failed to execute 'setAttribute' on 'Element': 'aria-disabled]' is not a valid attribute name.
• Error: Cannot read properties of undefined (reading 'filter')

The problem can be reproduced using this StackBlitz sample: https://angular-baaosj.stackblitz.io

Expected: Clicking on an item in the legend is supposed to toggle it's visibility.

Using kendo-angular-charts 5.1.0, if you add a series input, this does not happen. A full, minimal reproduction of this issue is available At the StackBlitz link below. The top chart has no issues (hides series upon clicking) while the bottom does.

https://stackblitz.com/edit/angular-5it8qu?file=app%2Fapp.module.ts

Screenshots of above repro:

It appears that there is a line deep in the codebase that says:

const seriesComponent = this.seriesComponents.get(index);
if( !seriesComponent ){ return; }
seriesComponent.toggleVisibility();

And the seriesComponents array is empty when you use the [series] binding.

We even went so far as to bind to the legend click event and toggle the visibility myself, but it is 100% ignored.
It was something like:

public onLegendClick(event: LegendClickEvent){
  event.series.visibility = !event.series.visibility;
  event.source.refresh();
  event.source.changeDetector.markForCheck();
}

Calling refresh did redraw the chart, but it was still visible/enabled. Even though digging into it with ng.getComponent on the kendo-chart, and looking at the series, it clearly showed series[0].visible to be false.

I had to make an assumption on version for this ticket since the dropdown on the bug report doesn't list 5.1.0. I wouldn't mind tips on understanding how to match up your marketing version name with your npm version. I spent 20 minutes looking around for that, but your versioning doc and release history don't seem to have anything about the actual version numbers used by package management.

I found a bug in your last update in this package:

https://www.npmjs.com/package/@progress/kendo-angular-dialog

The bug causes the modal not to show up.

In this bug you need to allways start the HTML files with the tag <kendo-dialog> and end the files </kendo-dialog> to fix the problem, which did not happen in previous versions of the package.

This bug is an issue because not even your tutorials work because of this.

Will you fix this?

Best regards André Lourenço

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 "popupSettings.appendTo" is set to 'component' then the value binding is broken and the "valueChange" event is not triggered.  It is not possible to select an item and the underlaying model is not updated.

Issue can be reproduced in this StackBlitz: https://stackblitz.com/edit/angular-f76kqf?file=src/app/app.component.ts

Regards

Holger

If ComboBox is used in a form and its required, screen readers will not pick up this information since it is not passed on to the underlying input field.

The example a nice workaround, but a final solution should have this automatically implemented by the control.

https://stackblitz.com/edit/angular-2ck3gu

https://stackblitz.com/edit/angular-niog8n-eldomz?file=app%2Fapp.component.ts

The date range picker is not closing when tabbing through inputs when the picker is appended to the 'component'. It also seems that once the date range picker loses focus, it does not close by clicking anywhere else in the document until it regains focus again or the document loses focus.

I reproduced it in Stackblitz and attached a video. In the video there is a button after the date picker that logs to the console when it gains focus. Focus starts at the top of the document, start tabbing until the date range picker pops up, then continue tabbing through the date range picker until the button below the picker gains focus. As you can see the date range picker does not close. Here is the Stackblitz editor link to this: https://stackblitz.com/edit/kendo-daterange-bug?file=app/app.component.ts

Thanks!

Mitchell

I very recently tried to update kendo UI to the latest version (from kendo-default-theme 4.23.0 to latest), and ran into a lot of problems, caused by the fact that I don't use the precompiled css theme styles. (removing the "node_modules/@progress/kendo-theme-default/dist/all.css" from the styles array in angular.json)

It is very opaque which styles needs to be imported for which module, and in what order they to be imported, since that seems to matter too.
Especially because there are no documentation for this at all.

For example, to get the styles for the new kendo-textbox component, the following needs to be imported in the styles.scss, AND in that specific order.

button needs to be first, and forms has to be before textbox and input

@import '~@progress/kendo-theme-default/scss/button/_index.scss';
@import '~@progress/kendo-theme-default/scss/forms/_index.scss';
@import '~@progress/kendo-theme-default/scss/textbox/_index.scss';
@import '~@progress/kendo-theme-default/scss/input/_index.scss';

which means that none of the following will compile: 

@import '~@progress/kendo-theme-default/scss/forms/_index.scss';
@import '~@progress/kendo-theme-default/scss/button/_index.scss';
@import '~@progress/kendo-theme-default/scss/input/_index.scss';
@import '~@progress/kendo-theme-default/scss/textbox/_index.scss';

@import '~@progress/kendo-theme-default/scss/button/_index.scss';
@import '~@progress/kendo-theme-default/scss/input/_index.scss';
@import '~@progress/kendo-theme-default/scss/forms/_index.scss';
@import '~@progress/kendo-theme-default/scss/textbox/_index.scss';

As i see it there are two reasonable ways to solve this, where the first obviously results in the best user experience:

• Refactor the styles "modules" to be 1:1 with either the angular module or the specific component, so using one module/component results in a single SCSS import only
• Create documentation that very explicitly states what files to import and in what order they need to be imported when using compiled SCSS

Hi, 

i'm trying to use the WindowService customizing the messages (tooltip) of the action buttons.

Seems that the custom labels are not shown and i have a console error

preview-2f5baf5affd53e419d85b.js:1 ERROR TypeError: Cannot set property 'closeTitle' of undefined

Here an example:

https://stackblitz.com/edit/angular-8z7vou

any suggestions?

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:

When resizing grid columns so the last column does not reach the right border of the grid (sum of columns width < current grid width), loading stored state (or changing column width property in any way) does not restore the columns width proportionaly to use the full width of the grid.

Note: in this case, the default columns width sum and stored state columns width sum are always inferior to the grid width in order to use proportionality and adapt to every screen size.

In our implementation, we made a "Reset columns view" (working exactly as the loading store data), but if the user play arround with the columns as described above), the reset is broken.

Reproduce steps:

Using the persisting state exemple available in the doc: https://stackblitz.com/edit/angular-3jdmzy?file=app%2Fapp.component.ts

- Click "Save current state"

- Resize grid columns so the last column does not reach the right border of the grid

- Click "Load saved state", the columns are resized proportionaly of the saved state but on the base of previous columns width sum instead of the full grid width.

Hi All,  

    Anyone can help us to figure it out?

   Currently, We are using Angular Kendo Gird package, and got issue for tooltip message for Gird.

        When We mouse move over 3 dots for grid column menu, we would get strange tooltip message,  for details , please check it from attachment.

         My Email:liji.tao@teranet.ca

Thanks

Liji

I'm using the Kendo Angular DropDownList component and I'm facing a couple of accessibility issues.

I got two issues, the same as those I get in my own application using the DropDownList component.
I've attached the output for both issues below.

First issue and an explanation of the issue and its solutions can be seen in the first attachment.

Second issue and an explanation of the issue and its solutions can be seen in the sercond attachment.