Describe the bug
When we use the Native Grid with a sortable configuration set to "{ mode: 'multiple' }" and we have a ColumnMenu, once the sorting functionality of the column menu is used, the sorting is reset.
To Reproduce
Expected behavior
The sorting shouldn't be reset no matter which Grid sorting functionality is used. In the above example, the sorting of the Discontinued column should be added to the complex sorting.
It will be a very nice feature improvement for the Menu if we can add a custom class to the popup of each menu item. Such a feature will allow us to easily customize the look of the popup itself, edit its position, etc.
The popup class can be configured using a property like "popupClass" or something else.
hhttps://stackblitz.com/edit/kgeavu?file=src/main.vue
the console.log is observed even when selecting other tabs.
Describe the bug
When having a movable Native Window component with a Grid inside it, the more cells(rows and columns) the Grid has, the slower the Window's rendering is. This effect is not replicable in the Kendo UI for jQuery scenario.
To Reproduce
Expected behavior
The rerendering of the Kendo UI for Vue Window should be smooth as it is in the Kendo UI for jQuery Window demo
Describe the bug
The layout of the column menu popup window, inside the Native Grid, is different when using version 4.x.x and version 5.x.x. of the Kendo Themes.
To Reproduce
Expected behavior
There should be a space between the different elements in the column menu -> filter popup
Describe the bug
In a scenario of Native Grid with Filter row once the filter popup is opened, the only way we can close it to select a value from the dropdown.
To Reproduce
Expected behavior
The popup of the filter should be automatically closed when it is blurred.
Describe the bug
When the PageChange event of the Native ComboBox or MultiSelect is triggered the following warning appears in the browser's console:
To Reproduce
Expected behavior
There shouldn't be any browser warnings when the pagechange event is triggered
Describe the bug
Both the ComboBox and DropDownList don't work as expected when configured in a virtualization scenario. The issue is related to skip value available in the event handler of the "pagechange" event. When you scroll the virtualized list down and then start to scroll in back in the upside direction, the value available in the event.skip property is at first being changed to a number that is bigger than the current "skip" value.
The result is that if you are currently at element 5000 in the popup list, and decide to scroll in the upside direction, the list will display items with an ID bigger than 5000 and the scroll in the upside direction will start from this new position.
To Reproduce
Expected behavior
When scrolling the items in the ComboBox or DropDownList components, the lists should behave the same way no matter if they are configured in a virtualization or default scrolling mode. When the list is scrolled, its items should move up or down without jumping to records that are not in the same direction as the scrolling.
Screenshots
If applicable, add screenshots to help explain your problem.
Describe the bug
In a Server-side rendering scenario, the tab navigation of the Native TabStrip is not visible right after its load. The tab navigation is not visible until the page gets rehydrated on the client side.
To Reproduce
Expected behavior
The tab navigation should be visible right after the page load, not when the page gets rehydrated on the client side
https://stackblitz.com/edit/mt45fg-d8vmdm?file=src/main.vue
The popup is Not appended to the div provided
The popup is appended to the div provided
Describe the bug
The appendTo and className properties of the Popup component cannot be set for the DropDowns, when configured through the popupSettngs prop.
To Reproduce
Expected behavior
We should be able to add a className to the component's popup and control the element to which the popup will be appended to.
The current implementation of the Native TreeView doesn't allow you to customize the expand/collapse arrows of the component.
Can you please provide a property that allows the definition of a custom class for a given TreeView group? Being able to define such a class, using CSS we can easily control the look of the different elements of each TreeView group.
Describe the bug
When we have multiple TimePickers on a page and start expanding their popups, the popups that are already expanded are not automatically closing.
To Reproduce
Expected behavior
The visible popup of a TimepPicker should be automatically closed when we expand the popup of another TimePicker
With the current implementation of the Native Grid, if one needs to set a minimum width to a column that needs to add the implementation suggested in this Setting a Minimum Column Width example.
While the approach in the above example works as expected, the logic that needs to be added can be internal for the Grid component. Thus the users will have to add a simple column property like the below and no other configuration should be set.
{
field: "ProductName",
title: "Name",
minWidth: 200
}
Describe the bug
By default, the Dialog component is a modal window. This means that once the Dialog appears, the page elements are the only ones the users can interact with.
Currently, if you use the keyboard navigation functionality of the Dialog, after pressing the Tab key multiple time, the focus will be on the "Open dialog" button below the modal. This should not happen.
To Reproduce
Expected behavior
When using the keyboard navigation of the Dialog component, the focus shouldn't be transferred to the elements below the modal area. It should be kept among the elements that are displayed in the Dialog.
Describe the bug
The position of the DropDownList's popup is not updated when the popup is opened above the component and the data items in the popup are filtered.
To Reproduce
Expected behavior
The bottom of the popup should be constantly stuck to the DropDownList and not staying at it initial position above the compoennt.
Screenshots
Add functionality that allows the users to configure the Native Grid's Pager in a way it has the "All" option in its page sizes DropDownList.
The "All" option is available in the Kendo UI for jQuery suite(check the second example on the page). When the "all" option is selected, all Grid records are loaded on one page.
Describe the bug
The DatePicker component behaves unexpectedly when it is part of an HTML form that has a Submit button. The things that happen are as follows:
To Reproduce
Scenario 1:
Scenario 2:
Expected behavior
When pressing Enter inside the HTML form, the form should be submitted and no DatePicker popups should open