onRowClick not there in Vue Grid 

Stackblitz example.

The Spreadsheet options are logged in the console in the mounted function. Note that pdf.proxyURL and excel.proxyURL have no values.

When using a grid with a selectable column and keyboard navigation enabled, it's not possible to select the last visible row. Instead of selecting the row, the grid just scrolls the item to the center of the grid.

I've attached a gif of the behavior and a sample project based on the grid demos.

Our front end team went through several frameworks before settling on Vue and nuxt.  From what I have been reading, nuxt is beginning to take off as a way to implement server side rendering of Vue.  It would be great if nuxt integration support were added to the Kendo Vue wrappers (or as a separate package if that makes more sense).

I want to fold / unfold all groups of the Grid with one click by placing

Currently in the Vue Native grid, you can only specify column widths in pixels.

This becomes problematic if the user has their browser font size set to a larger size. Since our font size, padding, etc. are using responsive rem units for sizing, they properly resize to a larger size, but since the column widths are set in pixels, the now larger filter fields and buttons don't fit appropriately in the alloted space (see below screenshot). For smaller columns, you can't even see what you've typed into the filter field.

In the screenshot, the larger font size was set in Google Chrome by going to Settings > Appearance > Font size > Very Large.

This enhancement would be helpful to ensure improved accessibility for those who need a larger font size in order to read the text.

 

 

 

Please extend Vue.js Grid Component with DetailTemplate like in AngularJS.

The Detail View of the Grid is very useful in combination with subcomponents, as I did always with AngularJS k-detail-template directive. By giving parameters to it it can be used really powerful.

I would like to use the same in Vue.js

Without the implementation of detail template as component or directive (But via script tag reference in options) no vue component is rendered inside.

I'm using Kendo UI with Vue wrappers. I have a grid that feeds from a remote datasource, but I have a custom implementation for the data service (using Axios). Currently, Kendo requires me to do this:
```
          <kendo-datasource ref="datasource" :data="rowData"></kendo-datasource>
          <kendo-grid :data-source-ref="'datasource'">
            <kendo-grid-column v-for="columnDef in columnDefs" :key="columnDef.field"
              :field="columnDef.field"
              :title="columnDef.headerName">
            </kendo-grid-column>
          </kendo-grid>
```

It seems like extra boiler plate to require the separate <kendo-datasource> tag. Why can't I bind my `rowData` directly to the kendo-grid?

Provide a local running installation package for the trial demo. Kendo UI for Vue

Does vue-cli v3 & kendoui R3 have support and demo programs?

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

I'd like to request the ability to create a Row Template in the Native Vue Grid similar to the Grid wrapper.  This way, I can use my custom Vue Components.

Just wanted to let you know that the CDN for Kendo Vue native grid suddenly stopped working today, about 1 hour ago. I hade to change @latest in the url to @0.3.4 (it automatically changed to 0.3.5 otherwise, and there's nothing there) to get my dev environment up and running again.

Goodmorning Progress,

We're working quite some time with Kendo for Vue and we are slowly migrating some old 'wrapper' grids to the new native grids. We know there are some limitations in it, because not everything is developed yet, but that wasn't a show stopper for us.

Or project uses quite a lot of data (like a google sheet) and we need it to be editable. So we implemented a native grid and a custom cell render with a VueComponent. This works perfect in case of a little amount of cells, but when there are more rows and columns it's giving us some performance issues.

First we tried virtual scrolling, but this feel 'honky-bonky' and is not even workable on a mac. Then we tried column-virtualization to minimize the rendered data, but also that didn't work. Columns aren't re-rendered when visible and its conflicting with our three locked start columns (visually data overlapping, numbers go through each other, etc).

Then our options are down to zero, so i started to investigate with some performance profiling what's happening. In our case we have 70 columns and 500 rows, this results in like 35k cells. Rendering isn't the big issue, until u start interact with the grid. Our RowClick-function sets one item in the data-items to 'inEdit' like the docs also showing. When this is happening the page freezes and i start wondering why. I found out that ALL the GridCell's (with a custom CellRender) are calling the updateRender-function. So 35k functions are called in some milliseconds and causes it to freeze. It takes around 30 sec's to get it a bit reactive, but you can understand its not workable anymore.

Our wrapper grids hadn't a single problem with handling these kids of data (no paging, no weird stuff, also custom renders for every cell)

Can you please provide me an answer why this is happening? It's possible to get access to our test-environment with the grids in action to visualize my problem a bit better. 

We have a payed license on a co-worker account (berend.haan@..).

Kind regards, 
Sander

Hi Kendo.

 

We're trying to replace Vue Grid Wrapper with the new Native Grid and most things works awesome. We only have one blocking feature that isn't inplemented yet.

 

So my question is when is the footer-logics comming for the native grid. We want to show aggregates in the fixed footer and it would be awesome it is like the 'headerCellRender' function defined on the grid. We know there is a gouping aggregate, but this isn't the thing we want.

 

Is there any idea when or even if it is comming to the native grid?

 

Kind regards,

Sander

Type in the Currency field in the example page here https://www.telerik.com/kendo-vue-ui/components/inputs/numerictextbox/formats/

 

After typing in the third digit, caret position moves to the 2nd digit instead of the first or last digit.

Typing in more digits causes the caret to move a position up occasionally.

 

Caret needs to be consistent on its positioning, either staying in the far left, or to the right before the decimal.

Preferably, this should be a prop to configure.

 

Also, tabbing out of the field when there are more than 2 decimal places will not format on leave.

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

For Vue components, the v-model on a multi-combo box and every component must bind to the underlying object.
:value-primitive="false" doesn't work as per some suggestions.

v-model binding to the underlying object is a MUST HAVE, Top priority, number one with a bullet. Without it, your components are a PITA to use and my current proof of concept might end here and we won't use your components with some bigger projects coming down the line.

Bug report

Vue Grid wrapper column template with router-link does not work correctly

Reproduction of the problem

https://codesandbox.io/s/vue-dynamic-components-t54dq

Current behavior

js errors

Expected/desired behavior

the router links work correctly

Environment

Do you have a development plan?