As of this moment the barcode components are only available in wrapper components. We would like to see a native Vue version for this aswell. Especially for the QR code option could be a big addition to the package
Hi there,
We create a dashboard like this:
We need to export in PDF format and we use the component:
https://www.telerik.com/kendo-vue-ui/components/pdf-processing/
Now we need to export in PNG or JPG format.
And this is our request: a Kendo Component that exports a dashboard with the same quality of the PDF component.
Thanks in advance.
The Spreadsheet component is among the last components in the Kendo UI for Vue suite that is available only as a Wrapper component.
Providing a Native version of the Spreadsheet will be a big improvement to the suite.
It would be great to have a clear button in the DatePicker, as today erasing value requires 3 select-delete operations (one for the day, one for the month, and one for the year)
It would make it consistent with TextBox, ComboBox, MultiSelect & AutoComplete, which renders in a comparable way
Hi there.
so the orgChart generates a great organizational hierarchy, but I want to be able to drag and drop elements to other parents like you can do with the Asp.net ajax version of the orgChart. How do I do this please?
Hello,
I noticed a bug with the Tooltip component, it can be reproduced here: https://www.telerik.com/kendo-vue-ui/components/tooltip/positioning/
In Tooltip.js there is a function called "handleMouseOut" that has this line:
const element = currentDocument && currentDocument.elementFromPoint(event.clientX, event.clientY);
Followed by:
if (isTooltipElement(element) || this.computedTarget !== event.target) {
return;
}
So when the mouseOut event is over the tooltip element, it is ignored, leaving the tooltip visible.
I was able to fix this by adding the following CSS styling to the tooltip element: `pointer-events: none;`, but now I may have introduced a new issue.
What is the reason for ignoring the mouseout event when it's over the tooltip?
Describe the bug
at Nuxt Environment
- pagable info option doesn't render information about the current page and the total number of records (both of setting true / false, all)
- set pageable info option false, error raise like this.
To Reproduce
- https://stackblitz.com/edit/nuxt-starter-mcocsr
Expected behavior
- render information about the current page and the total number of records
- do not error raise
Hi,
I would like to offer some suggestions for a few new icons to be added to the Progress Design System. I am currently trying to replace other libraries with the Kendo UI for Vue components, and these are a few icons I use for which I could not find a suitable replacement in the ones you provide. Please see the attached image for examples.
Also, it would be nice to have a "filled-in" version of some of the existing icons. For example, some current icons like "file-add" or "comment" are good, but they don't stand out at a smaller size. Having a solid color version (instead of just an outline) would provide options for bolder colors and make them more visible.
Thanks!
The following packages should be added as peer dependencies to the @progress/kendo-vue-data-tools package:
Describe the bug
The @progress/kendo-licensing is missing as peer to data-tools package
Nuxt 3 has a robust module system, which is highly beneficial for importing components easily. I have previously used modules like element-plus, headlessUI, and Vuetify. However, as we are currently transitioning to Kendo UI, we have encountered difficulties in finding a similar module. It is essential for us to be able to import Kendo UI components seamlessly and efficiently. Therefore, we have developed a module similar to the one for element-plus. During the process of writing and testing the code, everything has fallen into place. However, we have encountered an issue with importing the UI DropDownList from the module. It would be greatly appreciated if Kendo UI could provide an official Nuxt 3 module.
out test module
KDropDownList not work but else compoents work good.
Hello. I found a Bug on PanelBar Component at Nuxt3 environment, so I wrote a ticket.
When I click <PanelBar/> component's item the following image error occurs. the component does not work properly.
(I wrote a component as it is Kendo UI for Vue Native PanelBar Overview Page)
Please Check this once.
stackblitz (PanelBar Test on Nuxt3 Demo): https://stackblitz.com/edit/nuxt-starter-rsgcyn
ps. I checked out that the bug doesn't occur in the Vue3 environment.
stackblitz (PanelBar Test on Vue3 Demo): https://stackblitz.com/edit/vitejs-vite-afatj1
Hi.
The PDF Viewer component is something that is available in some of the other Kendo products like KendoReact, Kendo UI for jQuery, etc. Can you add the component also in the Kendo UI for Vue Native suite?
The PDF Viewer will be a nice feature that will make the Vue suite even better.
When providing the input prop ariaLabelledBy, the resulting rendered element has an attribute of arialabelledby instead of aria-labelledby.
That is, this code:
<span id="my-input-label">My Input Label</span>
<Input aria-labelled-by="my-input-label" />
results in this HTML:
<span data-v-0b8cedaa="" id="my-input-label">My Input Label</span>
<span data-v-0b8cedaa="" class="k-textbox k-input k-input-md k-input-solid k-rounded-md k-required">
<input id="58c2f77d-91e5-444a-a948-90f4abb960e5" required="" arialabelledby="subject-label" class="k-input-inner">
</span>
But the input's HTML should instead look like:
<input id="58c2f77d-91e5-444a-a948-90f4abb960e5" required="" aria-labelledby="subject-label" class="k-input-inner">
Describe the bug
Importing Kendo UI components results in our WebPack build producing the incorrect "dist" output.
Sometimes Webpack build adds additionalType.d.ts files and their directories to the dist folder
More information can be found in ticket:1602899
Hey there!
It would be great to add an option to the <Grid /> component that allows specifying a custom cell template specifically for the "select" column.
Looking at the documentation, there is an example that shows how to do something similar, but it overrides the complete CellRenderer for all columns.
Here is a minimum example of the API we could have:
<script lang="ts" setup>
import { Grid } from '@progress/kendo-vue-grid';
</script>
<template>
<Grid
selected-field="selectedField"
selected-cell="mySelectCell"
>
<template #mySelectCell="{ props }">
<!-- Checkbox or whatever you want -->
</template>
</Grid>
</template>
Kendo Splitter component `change` event is triggered from child components e.g. Input/Grid. I have multiple splitters defined, but only parent splitter has `onChange` event listener defined. When changing the text from child containing Kendo Input component which has no change event defined (doesn't really matter if it is), the event is propagated to Splitters `onChange` event and crashes Splitter pane handling. Added `onChange` listener to other Splitters as-well, they all are triggered. Clicking on Grid component checkboxes (is child to Splitter) to select the row will also trigger Splitters `onChange` event. Current workaround is to defined Splitters `@change` event as `@change.self` then the children's `change` events wont trigger it.