So the one feature we use a lot in our company revolves around PDF viewing and Image viewing within a component, where we display two or more at the same time.  Showing an image is easy, but we have lots of requests for it to be zoomable and after you zoom moveable to look at parts of the image.  Same goes for the PDF as we need to display it in a component next to another PDF as it is part of our Quality Check process.  And when they are side-by-side they would like to be able to move and zoom each one individually.  

Thanks,

Bill

$scrollview-pager-item-border-width is currently set to "0", but should be "0px", or maybe the calc needs to ensure there is a unit with something like (untested) @if(unitless($scrollview-pager-item-border-width), #{$scrollview-pager-item-border-width}px, $scrollview-pager-item-border-width)

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?

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.

Hi,

The example at the following URL is broken. See the attached screenshot for more details. Kindly fix asap. Thanks.

Regards,

Al

Starting with version "4.2.3" the LanguageService fails to be injected into the DialogTitleBarComponent.

This can be easily reproduced in the Single Component Rendering demo.

Link to StackBlitz: https://stackblitz.com/edit/angular-mprlwl?file=app/user-info.component.ts

Kindest regards,
Holger

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

Default Bootstrap buttons has this strange shadow or border issue

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

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

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

by rendering console show this error

Describe the bug
The <kendo-chart-series-item> component is missing settings for median and mean elements rendered by Box Plot series.

These are the two lines within each box (dashed line is mean):

Expected behavior
These series elements should be customizable and should accept an object containing color, width, dashType and opacity.

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

How to reproduce:

1.- Make a grid with master detail

2.- In master detail make a grid

3.- Create a context menu with options for the grid with a method so that when you click an option from the context menu it does something (console.log('Hello') for example)

4.- Create a context menu with options for the subgrid with another method so that when you click an option from the context menu it does something different (console.log('Goodbye') for example)

5.- When you click on an option from the context menu of the subgrid it will not call its function (console.log ('Goodbye')), it will call the function that triggers the context menu of the grid that contains the subgrid (console.log('Hello')

Even if a function is not set in the context menu of the subgrid it calls the function from the top context menu.

I solved it using 1 function for all context menus, but it doesn't seem like the best way to me

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

In Version 74.0.3729.108 (official Build) (64-Bit) of chrome, a defined grid with no predefined style property does not scroll properly. 

There is a live-demo on Stackblitz at https://stackblitz.com/edit/angular-b38r7s-jzsgty

This is a fork of the demo example from the kendo-angular-ui documentation available at

https://www.telerik.com/kendo-angular-ui/components/grid/scroll-modes/virtual/#

In the example, the scrollable grid was defined with a height property. This does not feet to our requirements, as we need a grid component that should flex according to the outside or parent container. 

This problem occured after the update of chrome browser from 73.0.XXX to the version 74.0.3729.108

The problem is fixed when we defined a grid with a height property like [style.height.%] = “100” but according to the documentation the grid should flex automatically without this property. 

Steps to reproduce:

Create fresh angular 9+ project : ng new angular9-kendo-editor-test

run cmd to add editor module: ng add @progress/kendo-angular-editor

Add config to serve es5 generated scripts so IE will work: https://medium.com/better-programming/how-to-fix-your-angular-app-when-its-not-working-in-ie11-eb24cb6d9920

run cmd to serve es5 config: ng serve --configuration es5

Open IE and browse to http://localhost:4200

Open developer tools, observe there is a script error

Comment out the EditorModule import in app.module.ts and you can see the app now works...