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

Hello Progress Software Corporation,

We currently have an issue with the Date Input (Calendar) KendoUI Angular component. We need to use the selection mode "multiple" when selecting a full week. When the component loads, it's possible to select a full week with no issue but once you start to play around with the infinite scroll, then another week is selected instead of the desired one. The bug can be reproduced directly in the example provided in your documentation.

https://www.telerik.com/kendo-angular-ui/components/dateinputs/calendar/multiple-selection/

For example,

1. Try to select a full week. It works.
2. Do the same with the next week
3. Now scroll to the next month and repeat 1 and 2
4. Repeat 3

Repeat this process for more than 4 months and you will see the bug where the selection of the full week jumps to a completely different month.

Kind regards,

Rodrigo Rosenblüth 

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

Dear Support,

we have upgraded our Kendo Angular Menu control from 2.0.3 to 3.0.4 and we are experiencing the following problem:

• in case the main menu item is displayed on the rightmost position of the page
• and the main menu item has submenu items
• the entire menu dropdown disappears while it tries to open and display the submenu items

please check the attached screen recording and the following stackblitz repro:

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

additional info:

• the problem cannot be reproduced in case the page has a visible margin on the right side
• unfortunately our design does not allow us to add a margin on the right side, so we need a different solution

Thank you,

Ferenc Papp

Kendo version :

How to reproduce :

- Add a kendo dropdown button with some items

- Use appendTo='component' popupSetting

- Bind itemClick and close events

Stackblitz example : https://stackblitz.com/edit/kendo-dropdownbuttons-keyboardnavigation?file=app/app.component.ts

What happens :

- If you use arrows to navigate through items, is always skip one item.

- If you use enter or space to select item, the popup close and reopen immediately.

- If you prevent close as in the stackblitz example : enter and space will fire twice the itemClick event.

There is a bug with the kendoGridGroupBinding directive when changing the input data and using virtual scrolling.  If you have many rows and scroll down to a lower virtual page and then change the input data to a small subset the grid will think there is no data.  And if you then change back to the full data set you have to start scrolling down before the grid repaints with data.  

Reproduction available here https://tyb2ys--run.stackblitz.io

Steps:

1. scroll down halfway in the grid

2. click the "Show subset" button.  Note the grid shows the no records message but should show three rows

3. click the "Show all" button.  Now the grid shows the scrollbar and the no records message is gone but it is not showing data.  You have to scroll down past where you previously were with all data before it repaints the rows

One workaround is to have an ngIf on the grid to destroy and recreate the grid when the input data changes, something like this:

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.

Use the basic usage example from https://www.telerik.com/kendo-angular-ui/components/dropdowns/multiselect/

Click in the area next to the baseball chip.

The list with available objects pops up.

Click in the place where the cursor is, the popup won't close.

Click in the right half of the component, the popup closes.

It seems it's the input element which swallows the click event.

I would expect the popup to be closed, no mather where I click in the component

We use PDF Export and include image files (png using an img tag (although I tried CSS as well when looking into this issue).  Recently we updated to Angular 10 and latest Kendo for Angular packages.

With Chrome there was no issue, but with IE 11, the images do not show up anymore in the exported pdf.

We isolated the change in behavior to @progress/kendo-drawing@1.9.1 - i.e. the images show up using 1.9.0, but do not using 1.9.1 or later versions.

Thanks

Hi,

Currently the kendo-datepicker submits the form when you press the enter key in the calendar popup.

I don't think this is the purpose? Can this be prevented please? If the current behaviour is useful in some scenarios, maybe provide a configuration option to alter this.

Thank you in advance.

Best regards,

Johan

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

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

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

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