I'm submitting a...

• Bug report

Current behavior

When the Date Inputs or DropDowns are positioned at the bottom of a page, their popup continues to open below the input field. This causes the popup to appear beyond the browser's boundaries, making the users unable to use the popup.

Expected behavior

The position of the popups of the Date inputs and DropDowns should be automatically changed based on the available space below each of the components. If there is not enough space to open the popup below the component's input, the popup should appear above the input.

Minimal reproduction of the problem with instructions

1. Open this StackBliz example
2. Click on the "Open in a New Window" button at the right corner
3. In the opened browser window, scroll to the bottom of the page
4. Open the popup of the DropDownList

I'm submitting a...

• Bug report

Current behavior

When defining a custom cell template by defining a new Vue component few Vue warnings appear in the console. Here are the errors:

• [Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders. Instead, use a data or computed property based on the prop's value. Prop being mutated: "dataItem"
• [Vue warn]: $listeners is read-only.

Expected behavior

There should be any errors in the console when defining a cell template using a Vue component.

Minimal reproduction of the problem with instructions

1. Open this Dojo example
2. Sort the Grid by any column
3. See the browser's console

Environment

Package versions: kendo-vue-grid 0.3.7 loaded via CDN

Describe the bug
The behavior of the Native and Wrapper MultiView calendars is different when using the next/previous arrows of the component.

The Native MultivVew calendar changes the selected date to the respective date of the next/prev month but doesn't change the month views as the Wrapper does.

Check the following two videos and see the differences:

Native.Multiview.Calendar-.Vue.mov

Multiview.Calendar.Wrapper.-.Vue.mov

To Reproduce

1. Open this StackBlitz project
2. Select a random date
3. Click on the "next" navigational arrow

Expected behavior
The same as the selected date should be focused on in the next month just like the Wrapper MultuView Calendar does.

I'm submitting a...

• Bug report

Current behavior

The user cannot select a filter operator if the filter input doesn't have entered data.

Expected behavior

The user should be able to pre-select a filter operator no matter if there is data entered in the filter input or not.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example
2. In the Product Name column, I click the filter operator button
3. Select "Ends with"
4. Click the filter operator button again and see that "Ends with" is not selected.
5. Type "g" in the filter text field. Grid updates but doesn't filter the data by "Ends with" filter.
6. Click the filter operator button and see that "Contains" is selected instead of "Ends with"
7. Select "Ends with" once more and Grid filters correctly

Describe the bug
The Tooltip is not correctly positioned in scenarios where a longer text needs to be displayed. This incorrect positioning leads to the inability to automatically close the Tooltip when the mouse is hovered out of the component.

To Reproduce

1. Open this CodeSandbox example.
2. Hover the yellow dot on the right

Expected behavior
The Tooltip should appear correctly positioned above the yellow point as it is in the scenario when you hover the left point in the above example

Screenshots

Describe the bug
The messages from the cldr-dates-full library are not loaded correctly in the Calendar component.
Month names in the Calendar control in Polish language should be in the nominative case.
Tooltips for the days in the calendar are in the genitive case and they are correct.

• The same issue could be replicable in other languages.

To Reproduce
Steps to reproduce the behavior:

1. Open this example.
2. See the translation of the month in the Calendar

Expected behavior
The month's name should be "listopad 2021". Instead, it is "listopada 2021". For reference, check this sample that uses the Kendo UI for jQuery suite and the messages are correct.

Screenshots

Describe the bug
When you use the filterGroupByField method, if there are more than 2 filtered items, the method returns null. If the filtered items are one or two, the method works correctly.

To Reproduce

1. Open this StackBlitz example
2. Open Browser's console(F12)
3. Click on the "ProductName" column menu and select 3 or more checkboxes
4. See the output in the console which is "null"

Expected behavior
The result returned from the filterGroupByField method should be with a structure similar to the below one, no matter how many checkboxes have been selected in the column menu.

Describe the bug
Locked and resized columns leave a small gap between the columns when scrolling is performed

To Reproduce
Steps to reproduce the behavior:
https://stackblitz.com/edit/mzxqs7-hy29kw?file=src%2Fmain.vue
lock both first and the second column from the column menu
resize the first column
scroll the columns

Curent -
A tiny gap is visible between the first and the second column

I am using Kendo Vue Wrapper Grid that is editable. I am using the propery 

:editable-create-at="bottom"

but the new rows are always added at the top.

There is another open issue related to this.

https://github.com/telerik/kendo-ui-core/issues/5198

 

Please provide a fix.

 

Hi Team,

KendoNative Multiselect which is configured to work with primitive values has issue with filtering

PFB link below for the demo

https://stackblitz.com/edit/habvwq-e4ahdk

Hello Team,

Icon for MS Word is missing the logo which is impacting UX for our application. Appreciate if this is resolved on priority

Reference in the Image: Docx 1. docx

Hello Team

Selection/Highlight of the Main Menu is incorrect, when the child item of different submenu is chosen. This is UI/UX glitch and would helpful if resolved

Code Snippet : https://stackblitz.com/edit/nrqsrn?file=src%2Fmain.js

Describe the bug
multiple false still allows more than one files dropped on windows

To Reproduce
https://stackblitz.com/edit/gvptz7-ltakhv?file=src%2Fmain.vue

Drop more than one file on windows
Expected behavior
it should not be allowed

Describe the bug
When using the GridPdfExport component for exporting Grid data to a PDF file the exporting operation fails with the following error:

• The issue is replicable only when working in Vue 2 context

To Reproduce

1. Open this CodeSandbox example
2. Click the button above the grid

Expected behavior
A system dialog should appear asking where the generated file should be saved

Steps to reproduce:

(latest version of vue, vue CLI, node etc. installed globally)

• vue create test-project
• cd test-project
• npm install --save @progress/kendo-ui
• npm install --save @progress/kendo-theme-default
• npm install --save @progress/kendo-dateinputs-vue-wrapper
• added Calendar component to App.vue (see https://www.telerik.com/kendo-vue-ui/getting-started/)
• changed the name "kendo-calendar" in HTML template to "Calendar", otherwise I get build errors
• npm run serve --> browse to localhost:8080 --> error in console:

Uncaught ReferenceError: $ is not defined
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:85)
    at Object.eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:292)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:74)
    at Object.1472 (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:75)
    at __webpack_require__ (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:21)
    at Object.0 (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:49)
    at __webpack_require__ (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:21)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:41)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:44)
    at Object../node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js (app.js:3624)

I could reproduce the error using different Kendo UI for vue components like Buttons etc. (following the getting-started page for the button component). The default vue project template uses Babel and Webpack. Is there a configuration missing for Kendo UI?

I already checked:

• https://www.telerik.com/kendo-vue-ui/getting-started/
• https://www.telerik.com/support/whats-new/kendo-ui?utm_medium=internal&utm_source=yellowribbon&utm_campaign=kendo-ui-vue-awareness-r22019release#vue-updates-in-r2-2019
• https://www.telerik.com/blogs/what-you-need-to-know-about-vue-cli-3
• https://www.telerik.com/blogs/better-tooling-with-the-new-vue-cli
• https://www.telerik.com/blogs/integrating-vue-cli-3-with-kendo-ui
• https://www.telerik.com/blogs/creating-and-managing-vue-projects-with-vue-ui

In Kendo UI Grid for jQuery we have the following:

"editable": {

    "createAt": "bottom"

}

 

How it can be done in Kendo Grid for Vue.JS ?

----------------------------------------------------------------------------------------------------------------------------------

Bug report

In Grid(Wrapper) in UI for Vue, the editable-create-at is not changing Grid's "add new row" behavior when it is set to "bottom".

Reproduction of the problem

1. Open this Stackblitz and run it
2. Press the "Add new record" button and see that the new record is being added to at the top of the Grid

A workaround that could be applied is to use :editable="{createAt:'bottom'}" instead of :editable-create-at="bottom"

Current behavior

The new rows are being added to the bottom of the Grid with :editable-create-at="bottom"configuration applied.

Expected/desired behavior

When :editable-create-at="bottom" is applied the new records in the Grid should be added to its bottom

Environment

• Kendo UI version: 2019.2.621
• jQuery version: x.y
• Browser: [all]

Describe the bug
Combobox does not scroll to focused item

To Reproduce
https://stackblitz.com/edit/u4crwa?file=src%2Fmain.vue

Type v

Expected behavior
Volleyball is scrolled into view

The issue is reported in ticket - https://supportheroes.telerik.com/ticket/1547173 and there is a project attached and the warning is this one:

telerik/kendo-charts#266

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

1. Open this StackBlitz example
2. Click on the icon next to a random input in the filter row
3. Click outside the popup that appears in step 2.

Expected behavior
The popup of the filter should be automatically closed when it is blurred.

Screenshots

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

1. Open this StackBlitz example
2. Click on the "Open in new window" button to open the example in a separate window/tab
3. In the new window, click on the "Open dialog" button
4. Once the Dialog is opened, press the Tab button 8 times and press Enter
5. The Dialog will be closed because, after the 8th Enter press, the focus will be again on the "Open dialog" button below the modal area.

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.