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
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:
Steps to reproduce:
Actual result: current value doesn't have selected styles in the dropdown
Expected result: current value in the dropdown is highlighted. Please see an example below:
Kendo version :@progress/kendo-angular-buttons: 5.4.1
How to reproduce :
- Add a kendo dropdown button with some items
- Use appendTo='component' popupSetting
- Bind itemClick and close events
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.
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,
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:
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.
<div class="form-group"> <kendo-editor *ngIf="!formDisabled" [(ngModel)]="securityplan.dataFlow" id="dataFlow" name="dataFlow" style="height: 250px; width: 100%;">. </kendo-editor> </div>
When you click into the body of the editor, "before emit" is console logged.
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.
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).
Custom editing in reactive forms within EditDialogTemplateDirective causes udefined error at EditDialogComponent.titleInput .
Reproducible at example https://www.telerik.com/kendo-angular-ui/components/scheduler/editing/custom-reactive-editing/
On the kendo-multiviewcalendar the 'activeViewDateChange' is not triggered, at all.
We need this event for our date range selection to update certain data. But without this event, it's impossible.
Is this a missing feature or a bug as almost every other date component has this event.
When a Grid cell is focused, and after this, the data is filtered so that the data contains fewer items than the index of the row the last focused cell was in, the Grid table area does not receive focus when tabbed into.
Please check the example:
It seems there is an issue with the material theme and nested grids. When you have master-detail nested grids, the entire last nested grid gets applied with the same styling as the bottom rows of all the other nested grid.
The styling in my browser is showing up as
Which causes the rows in the last grid to not appear.
I have attached an image where I have changed the styling to 5px and red so you can see that it is being incorrectly styled. You can see that even the other rows in in the last grid are getting styled along with the last row style.
I am running the latest version of Kendo.
I've created a Plunker: http://plnkr.co/edit/WoqkaDZpq8hU24m0eKcv?p=preview Show the detail template of Row 1 in Beverages, then collapse the Beverages group. the Detail for Chai does not go away with the rest of the table.
I am trying to access the documentation for Kendo UI for Angular and I am getting a redirect error in the browser (Chrome and Firefox), specific to the Kendo Grid documentation for filtering: https://www.telerik.com/kendo-angular-ui/components/grid/data-operations/filtering/
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.
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.
if editor recive a value like '<span class="platzhalter">Empfaenger_Debitor</span>'
by rendering console show this errorcore.js:15724 ERROR TypeError: Cannot read property 'split' of null