Currently in Vue we don't provide the ability to share with the customers the source code before the compilation but just the already compiled code.

We need to provide the ability to fork the repository and build components from the Vue repository similarly to the way it is done in Angular and React. 

Add resources (documentation and code) for Composition API.

Describe the bug
DropdownTree component throws an error when user opens dropdown menu when they selected an item already, if valueRender prop is configured.

To Reproduce
Steps to reproduce the behavior:

1. Open this example - https://codesandbox.io/p/sandbox/3tmtkk?file=%2Fsrc%2Fmain.vue
2. Select any item from DropdownTree. No errors would be thrown.
3. Try to press on dropdown tree to open dropdown menu again.
4. User will see this error instead of dropdown tree menu opening.
   

Describe the bug
A licensing warning may continue to appear in the browser's console, no matter whether the licensing activation has been successful or not.

The issue is replicable when the user trying to activate a license has had an active license in the past and this license is already expired.

To Reproduce
Because of the specifics of the issue, a project in which the bug can be replicated won't be publicly provided.

Expected behavior
The license activation process should activate one's license no matter the previous licensing history of the user

The problem occurs only on a component DropdownTree in which the filtering fonctionality is enable.

I have this problem when testing on Chrome and Firefox.

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, 
Drag and drop an image inside editor isn't working in Chrome. 
sometimes the images is opened in new tab, sometimes the image path is added. 

However, it works on Firefox.

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
The @progress/kendo-licensing is missing as peer to data-tools package

The following packages should be added as peer dependencies to the @progress/kendo-vue-data-tools package:

• "@progress/kendo-svg-icons"
• "@progress/kendo-vue-popup"
• "@progress/kendo-vue-animation"

Describe the bug
The following error appears when activating the license of the Native Vue suite with Node 21.3.0

To Reproduce

1. Install node 21.3.0
2. Run npx kendo-ui-license activate
3. See the unsuccessful activation error

Expected behavior
The license activation should work with all Node versions

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

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">

I was looking through the documentation for the native drop down list and did not see an example for grouping like the wrapper drop down list has. https://www.telerik.com/kendo-vue-ui/components/datasource/datasource/grouping/ I would like to request a group functionality for the native drop down list.

Hi. 

I am looking for a Badge component in the Kendo UI for Vue suite. The component is available for the Angular suite(https://www.telerik.com/kendo-angular-ui/components/indicators/badge/) but not for Vue.

It will be nice to have this component available also for Vue.

Hi Team,

Can you consider the implementation of a Native TileLayout component? 

It will be a very nice add-on to the Native Vue suite.

New Native Vue DropDownTree Component

Describe the bug
When using a slot to define the columns in the Wrapper Grid, the result in Vue 2 and Vue 3 is different.

• In Vue 2, if we pass 2 columns to the slot, only these two columns are rendered in the component.
• In Vue 3, no matter how many columns we pass to the slot, the component renders all columns, based on the data in the datasource

To Reproduce
Check the two examples below:

• Vue 2 - https://codesandbox.io/s/jovial-hamilton-k6hfl7?file=/src/App.vue
• Vue 3 - https://codesandbox.io/s/empty-smoke-cnyz0t?file=/src/App.vue

The two examples use the same implementation but the number of columns rendered in each Grid is different

Expected behavior
The two examples should work the same way as in the Vue 2 application.

Screenshots
Vue 2:

Vue 3:

The DatePicker, DateTimePicker, TimePicker, and DateRangePicker components don't provide open and close events that are triggered when the popup of a component is opened/closed. 

 

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.