Unplanned
Last Updated: 26 Jan 2023 19:36 by ADMIN
Scheduled for R2 2023 - Increment 1 (01.03.2023)

Describe the bug
The Native Signature component throws the following error when its popup is minimized:
image

To Reproduce

  1. Open this StackBlitz exmaple
  2. Open the popup of the Signature component
  3. Check the browser's console where the above error will appear
  4. Close the popup
  5. The above error appears for a second time inside the console

Expected behavior
There shouldn't be any errors when opening/closing the popup of the Signature component.

Completed
Last Updated: 25 Jan 2023 15:36 by ADMIN
Release R2 2023 - Increment 1 (01.03.2023)
Created by: n/a
Comments: 0
Category: Kendo UI® for Vue
Type: Bug Report
0

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

image
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
image
The above should be changed to:
import { hasParent } from './utils/index.js';

Expected behavior
The described above exports should point to existing files

In Development
Last Updated: 25 Jan 2023 13:55 by ADMIN
Scheduled for R2 2023 - Increment 1 (01.03.2023)

Describe the bug

When we have more than one locked column in a TreeList and scroll the content of the component horizontally, in scenarios when two locked columns are one by one, the layout of the component is breaking.

To Reproduce

  1. Open this StackBlitz example
  2. Scroll the TreeList horizontally to the left
  3. See that only the header of the Position column is not moving, while the data of the column is moving along with the data of the other columns.

Expected behavior
The first two columns(Name and Position) should stay locked and the content of the other columns should be scrolled below them.

Screenshots
image

Unplanned
Last Updated: 25 Jan 2023 07:11 by ADMIN
Scheduled for R2 2023 - Increment 1 (01.03.2023)

Describe the bug
The value of the data-grid-row-index attribute of the different Native Grid rows is always -1, no matter the scenario in which the component is used.

To Reproduce

  1. Open this StackBlitz example
  2. Inspect a random Grid row and see its attributes

Expected behavior
The different rows inside the Grid should have different values for the data-grid-row-index attribute.

Unplanned
Last Updated: 25 Jan 2023 06:37 by ADMIN
Scheduled for R2 2023 - Increment 1 (01.03.2023)

Describe the bug
With the current Upload implementation, the component doesn't provide an option to filter the files that are selected for upload if the auto-upload property is set to true.

Currently, the files can be filtered only if the auto-upload is set to false as in this StackBlitz example.

To Reproduce

  1. Open this StackBlitz example with auto-upload property set to true
  2. Select multiple files + one that has the letter "g" in its name

Expected behavior
The file with the letter "g" should not be uploaded

  • As a possible solution for the issue, we can provide an event that is triggered before the file upload and when the event is triggered, the files will be filtered.
Completed
Last Updated: 20 Jan 2023 15:28 by ADMIN
Release R1 2023 - Increment 3 (18.01.2023)

Describe the bug
When using the item property of the RadioGroup, the properties of each item are not passed to the template and thus a custom template with dynamic data cannot be created.

To Reproduce

  1. Open this StackBlitz example and see the generated result

Expected behavior
The items defining the RadioGroup elements should be available in the template passed to the item property

Completed
Last Updated: 20 Jan 2023 13:54 by ADMIN
Release R1 2023 - Increment 2 (07.12.2022)

Describe the bug

In a Native Editor scenario, if you open the View HTML window, the window can be closed only using the two buttons at its bottom.

To Reproduce

  1. Open this StackBlitz example.
  2. Click on the View HTML button.
  3. Try to close the window using the "x" button in the upper right corner.

Expected behavior
The popup window should be closed when the "x" button is clicked

Completed
Last Updated: 20 Jan 2023 13:41 by ADMIN
Release R1 2023 - Increment 2 (07.12.2022)

Describe the bug
The following JS error appears in the console when using the Insert Table tool of the Native Editor without choosing a table size to insert.

To Reproduce

  1. Open this StackBlitz example
  2. Click on the "Insert table" tool to open a popup
  3. Click outside the popup

Expected behavior
No JS should appear when the user opens the popup of the "Insert Table" tool and doesn't select a table size in it.

Screenshots
image

Completed
Last Updated: 20 Jan 2023 13:35 by ADMIN
Release R1 2023 - Increment 3 (18.01.2023)

Describe the bug
The current implementation of the Native Scheduler component is not affected by the Internationalization configurations applied to it.

To Reproduce

  1. Open this Globalization Demo
  2. In it, the IntlProvider is defined with a locale value of es
  3. Having the above configuration, the first weekday in the Week view should be Monday, while, in the example, the first day is Sunday

Expected behavior
The Scheduler should accept both the Localization and Internationalization configurations applied to it.

Unplanned
Last Updated: 19 Jan 2023 10:29 by ADMIN
Scheduled for R2 2023 - Increment 1 (01.03.2023)

Describe the bug
There is a blank space at the bottom of the Grid when the user scrolls the data. This blank space appears on a specific configuration where the Native Grid is configured with virtual scrolling and the groupable property is set as follows:

:groupable="{ footer: 'visible' }"
  • The issue is replicable in both Vue 2 and Vue 3
  • The issue is not replicable if the groupable prop is defined like this:
:groupable="true"

To Reproduce

  1. Open this StackBlitz example
  2. Scroll the data items to the bottom of the Grid

Expected behavior
There shouldn't be any white/blank spaces at the bottom of the Grid

Screenshots
image

Need More Info
Last Updated: 18 Jan 2023 15:16 by ADMIN
Created by: Sinuhe
Comments: 1
Category: Tooltip
Type: Bug Report
2

@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 try this was by:

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 })
}
But the events are just not triggered, so we cannot properly test our implementation.
Duplicated
Last Updated: 18 Jan 2023 13:12 by ADMIN
Created by: Sanatan
Comments: 0
Category: Kendo UI® for Vue
Type: Bug Report
0

@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 })
}
But the events are just not triggered, so we cannot properly test our implementation.
Unplanned
Last Updated: 12 Jan 2023 08:32 by ADMIN
Scheduled for R1 2023 - Increment 3 (18.01.2023)

Describe the bug
The TreeListDataStateChangeEvent type currently has the following props:

  • component, dataState and event

While its props should be:

  • component, data and event

Expected behavior

The types defined in the TreeListDataStateChangeEvent should be component, data, and event

Unplanned
Last Updated: 05 Jan 2023 09:04 by Daniel Grünberger
Created by: Daniel Grünberger
Comments: 0
Category: Tooltip
Type: Bug Report
0

Describe the bug
The Native Tooltip is not hiding when the mouse cursor is moved fast from the target element in the direction where the Tooltip is about to appear.

To Reproduce

  1. Open this StackBlitz
  2. Hover the Button and move fast the mouse cursor to right(covering the area of the Tooltip)
  3. Repeat step 2 multiple times if the Tooltip hides

Expected behavior
The Tooltip should disappear when the mouse cursor is moved away from the target element no matter the direction in which the cursor is moved.

Screenshots
image

Completed
Last Updated: 06 Dec 2022 12:41 by ADMIN
Release R3 2022 - Increment 2 (03.08.2022)

Describe the bug
When we have multiple TimePickers on a page and start expanding their popups, the popups that are already expanded are not automatically closing.

To Reproduce

  1. Open this StackBlitz example
  2. Click on the "clock" icon of a random TimePicker to open its popup
  3. Repeat step 2 over other randomly selected TimePicker

Expected behavior
The visible popup of a TimepPicker should be automatically closed when we expand the popup of another TimePicker

Screenshots
image

Unplanned
Last Updated: 01 Dec 2022 15:59 by Yi

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

Unplanned
Last Updated: 30 Nov 2022 09:40 by ADMIN
Scheduled for R1 2023 - Increment 2 (07.12.2022)

Describe the bug
When the Grid's resizable property is set to true, the following test fails:

import { describe, it, expect } from "vitest";
import App from "../App.vue";
import { render } from "@testing-library/vue";

describe("App.vue", () => {
  it("renders apps", async () => {
    render(App);
  });
});
  • The issue is not replicable if in Draggable.js file the:
import KendoDraggable from '@progress/kendo-draggable';

is changed with:

import { Draggable as KendoDraggable } from '@progress/kendo-draggable';

With this error:
image

To Reproduce

  1. Open this project
  2. Run 'npm install'
  3. Run 'npm run test:unit'

Expected behavior
The test should pass as it used to pass in version 3.5.0, for example.

Unplanned
Last Updated: 18 Nov 2022 13:07 by Sviluppo

Describe the bug
When activating the keyboard navigation inside the Native Grid and there are custom cells in this Grid, the navigation between the cells(in a specific scenario) is slow.

Scenario: In a Grid whose cells are all custom, focus a random cell in the first column. Then press and hold the right keyboard arrow. The focused cell starts moving to the right and then freezes until the last Grid column is reached.

Here is a video demonstrating the described scenario: https://user-images.githubusercontent.com/41293735/202707680-1964d01e-dbd3-4a35-93c4-1dbcfd45e887.mp4

  • The issue is replicable on Chrome and Chromium-based browsers, on Windows 10.
  • Testing the scenario on Firefox(Windows 10), the issue cannot be reproduced.

To Reproduce
Steps to reproduce the behavior:

  1. Open this StackBlitz example on Windows and Chrome/Chromium-based browser
  2. Focus a cell in the first column of the Grid
  3. Press and hold the right keyboard arrow

Expected behavior
The movement of focus inside the Grid should be smooth and visible

Unplanned
Last Updated: 08 Nov 2022 11:51 by Alex

Describe the bug
When expanding/collapsing grouped data in the Grid re-renders all Grid rows while only the collapsed ones should be re-rendered.

To Reproduce

  1. Open this CodeSandbox
  2. Collapse a group
  3. Open the browser's console and see that row-render has been called 1000 times

Expected behavior
The row-render method should be called for the rows that hold the collapsed data, not for all Grid rows.

Unplanned
Last Updated: 03 Nov 2022 07:02 by ADMIN
Scheduled for R1 2023 - Increment 2 (07.12.2022)
Created by: n/a
Comments: 0
Category: Kendo UI® for Vue
Type: Bug Report
0

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

1 2 3 4 5 6