Describe the bug

When the Localization and Intl Providers are used in Vue 2 with Composition API, there is an error in the browser's console that appears initially, before any user interaction. The error is "[Vue warn]: Error in data(): "TypeError: ref is not a function"". After this error appears, no matter what values are passed to both the Localization and Intl components, the are not functioning.

To Reproduce

1. Open this CodeSandbox example
2. Open the browser's console and see the error.

Expected behavior
The Localization and Intl Providers should work correctly in both options and composition API contexts

Screenshots

Describe the bug
When binding the Scheduler Wrapper component to a remote datasource, there are two requests sent to the remote service.

To Reproduce

1. Open this StackBlitz example and run it.
2. Open the Network tab of your browser and see the requests

Expected behavior
Only one request should be sent to the remote service

Screenshots

We have a window hidden with v show and a DatePicker in it.
When we open the DatePicker and try to hide the Window the popup of the DatePicker stays opened

example and steps in ticket - 1562574

workaround - delay the hiding of the Window with 200 ms to ahve a default hiding of the popup executed:

const toggleDialog = (e) => {
e.preventDefault();
setTimeout(() => {
if (visible.value) {
showPopup.value = false;
}
visible.value = !visible.value;
}, 200);
};

Describe the bug
When working with the Wrapper DropDownList, if the component uses the v-model directive, there are some white spaces appearing in the popup of the component.

If the component doesn't use the v-model, the described behavior is not replicable.

To Reproduce

1. Open this StackBlitz example.
2. Select "Fish"
3. Select "Pizza"
4. Repeat steps 2 and 3 multiple times
5. See the white space in the popup

Expected behavior
No white space should appear in the popup of the DropDownList component.

Screenshots

When entering a number with decimals in a Native NumericTextBox with a format it rounds up the number if you enter more decimals than the format allows. In this Stackblitz project you can see this behavior.

In the Wrapper NumericTextBox it is possible to add a round property with the value false which prevents the rounding of decimal numbers. Instead of rounding it truncates the number. By my knowledge and what I can find in the Vue documentation this property isn't available in the Native NumericTextBox.

Proposed solution
Add round property with related logic to the native component.

Steps to reproduce

1. Copy and paste the value 12.345
2. See that the value in the input becomes 12.35
3. See that :round="false" does nothing.

Describe the bug
The rowReorder event is missing in the Wrapper Grid component, while it is available in the Kendo UI for jQuery Grid. Currently, the only way the event can be used is by using a code like the below in the mounted hook of the Vue app:

    var grid = this.$refs.grid.kendoWidget();
    grid.bind('rowReorder', function (e) {
      console.log('row', e);
    });

Expected behavior
The rowReorder event should be available for usage as the other events of the Wrapper Grid

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

@open and @close events are not triggered by integration testing tool, even when programmatically calling the event.

We are using cypress 11.1.0

cypress-real-events: 1.7.4 was also used to try of trigger the events but didn't work.

The way we tried this was:

cy.get(element).trigger(‘mouseover’)
cy.get(element).realHover()
cy.get(element).trigger(‘mouseover’)
cy.get(element).trigger(‘mouseenter’)
cy.get(element).then(el => {
    el.dispatchEvent(new MouseEvent(‘mouseenter’, { bubbles:true })
}

Describe the bug
There is an incorrect export inside the @progress/kendo-vue-inputs package on line 39 in the @progress/kendo-vue-inputs/dist/esm/main.js file

This import fails because this file does not exist. When we change the above line to:
export * from './signature/interfaces/index.js'; everything works as expected.

A similar issue is found in the following file: @progress/kendo-vue-inputs/dist/esm/signature/Signature.js on line 145

The above should be changed to:
import { hasParent } from './utils/index.js';

Expected behavior
The described above exports should point to existing files

Hello,

The StackLayout component is available in other Kendo UI suites like KendoReact for example but is still not provided for Vue. Can you add the StackLayout component to the Kendo UI for Vue Native suite?

Hello,

The GridLayout component is available in other Kendo UI suites like KendoReact for example but is still not provided for Vue. Can you add the GridLayout component to the Kendo UI for Vue Native suite?

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.

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>

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

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

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.

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.

• certificate/award/ribbon
• thumbs-up/thumbs-down
• flag

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!

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

Hello,

I noticed a bug with the Tooltip component, it can be reproduced here: https://www.telerik.com/kendo-vue-ui/components/tooltip/positioning/

1. Hover where it says HOVER ME until the tooltip shows up
2. Move the mouse up very quickly. When the mouseout event is over the tooltip, the tooltip does not close -> NOK, the tooltip is open, but the mouse is no longer over the element

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?