Completed
Last Updated: 08 Aug 2022 13:17 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

Completed
Last Updated: 12 Jul 2022 10:25 by ADMIN
Release R3 I1 June 2022

Describe the bug
When using the Auto-Resizing in combination with the Appearance size the Auto-Resizing isn't triggered again after the Appearance size has been changed. Because of this, the Native TextArea stays to 'big'. The Auto-Resizing is only triggered again when you change the value of the TextArea.

To Reproduce
Steps to reproduce the behavior:

  1. Open this StackBlitz example
  2. Fill in a value
  3. Switch the 'Size' DropDownList value to 'Large'.
  4. Switch the 'Size' DropDownlist value to 'small'.
  5. Additional white space is visible below the value.
  6. When changing the value the Auto-Resizing is triggered again.

Expected behavior
The TextArea should be resized automatically when changing its "size" appearance property, without the need to update the value of the component

Completed
Last Updated: 22 Jun 2022 08:18 by ADMIN
Release R3 I1 June 2022

Describe the bug
Then using the Native Tooltip with Icon tag or SVG, the component is displayed aside from the hovered element.

To Reproduce

  1. Open this StackBlitz example
  2. Hover either the Icon element or the SVG

Expected behavior
The Tooltip should appear exactly below the hovered element.

Screenshots
Icon:
image
SVG:
image

Completed
Last Updated: 30 May 2022 12:51 by ADMIN
Release R3 I1 June 2022

Describe the bug
When we have a NumericTextbox with formatting set to "p1", "p3"..."pX"(percentage with X decimal numbers) the component is not working correctly when we try to manually enter a value in it.

  • The issue is replicable when you select the content of the component and delete it, before entering a new value. If there is a value in the NumericTextbox and one just selects it and changes it, the issue is not replicating.
  • The issue is not replicable if you use a formating of "p", without a decimal numbers definition

To Reproduce

  1. Open this StackBlitz example
  2. Select the value in the NumericTextbox and delete it(The NumericTextbox should be empty)
    image
  3. Try to enter 5.75

Expected behavior
The user should be able to manually enter a value by pressing "5" + "." + "7" + "5"

Screenshots
download

Completed
Last Updated: 26 May 2022 05:56 by ADMIN
Created by: Seuthes
Comments: 2
Category: TabStrip
Type: Bug Report
0

When you select a tab, the tab headers are completly redrawn. This makes it impossible to add CSS transitions and animations to the tabs. I would like to add an transition to `.k-state-active`, so on selection there is a nice transtion.

Instead of redrawing, only the necessary changes should be applied to the items, i.e. changing CSS classes.

Completed
Last Updated: 25 May 2022 12:20 by ADMIN
Release R3 I1 June 2022
Created by: Shashwat
Comments: 0
Category: Tooltip
Type: Bug Report
0

Tooltip stays opened when the mouse is in and our fast and it goes through the tooltip itself. video in ticket - 1563700
https://stackblitz.com/edit/vue-cyjfhr?file=src%2FApp.vue

Completed
Last Updated: 23 May 2022 14:39 by ADMIN
Release R3 I1 June 2022

Bug report:
https://stackblitz.com/edit/bbuqh1?file=src/main.vue

Steps:
Focus the input, type some text and blur -

Current:
an warning is observed in the console and the types string is passed to the change event.

Expected:
an warning is observed in the console and the types string SHOULD NOT BE passed to the change event.

Completed
Last Updated: 23 May 2022 14:38 by ADMIN
Release R3 I1 June 2022

Describe the bug
The "ghost" element that appears when we try to resize an event in the Scheduler is missing in the Timeline and Month views. The result is that the users don't have a visual representation of what is the new size of the event they are modifying. The resizing itself is working correctly. The issue is only with the visual representation.

To Reproduce

  1. Open this StackBlitz example
  2. From the Views in the upper right corner select "Timeline" or "Month" view
  3. Select a random event and try to resize it.

Expected behavior
An element that shows the possible new size of the event should appear like it is in the Day view, for example.

Completed
Last Updated: 23 May 2022 14:35 by ADMIN
Release R3 I1 June 2022

Describe the bug
In scenarios when we have a color applied to a Scheduler resource, the pre-defined color is not visualized as a background if we use the group prop. This happens when the resource is not available in the array passed to the group property. If the resource that holds a color is available in the group array, the colors are correctly displayed.

To Reproduce

  1. Open this StackBlitz example
  2. See the 4 events available in the view

Expected behavior
The events assigned to Room 1 should be with blue background and the events assigned to Room 2 should be with red/pink background. This should be valid for all scenarios in the Scheduler - with and without grouping.

Screenshots
image

Completed
Last Updated: 20 Apr 2022 05:08 by ADMIN
Release May 2022
Created by: Andreas
Comments: 0
Category: Kendo UI® for Vue
Type: Bug Report
0

https://stackblitz.com/edit/gv4uwk?file=src/main.vue

Focus the initial input then press tab
the stepper is focused yet it does not change visually so we know it

expected:
There is a visual initial representation of the focused component

Completed
Last Updated: 13 Apr 2022 12:54 by ADMIN

Describe the bug
The messages from the cldr-dates-full library are not loaded correctly in the Calendar component.
Month names in the Calendar control in Polish language should be in the nominative case.
Tooltips for the days in the calendar are in the genitive case and they are correct.

  • The same issue could be replicable in other languages.

To Reproduce
Steps to reproduce the behavior:

  1. Open this example.
  2. See the translation of the month in the Calendar

Expected behavior
The month's name should be "listopad 2021". Instead, it is "listopada 2021". For reference, check this sample that uses the Kendo UI for jQuery suite and the messages are correct.

Screenshots
image

Completed
Last Updated: 12 Apr 2022 06:35 by ADMIN

Describe the bug
The Native Editor blocks the browser when used in Vue 2. Meanwhile, the same component configuration works correctly in Vue 3.

To Reproduce

  1. Open this CodeSandbox(Vue 2)
  2. The project cannot be started or blocks the browser

Expected behavior
The example above should be working like in this project(Vue 3).

Completed
Last Updated: 04 Apr 2022 12:24 by ADMIN

Describe the bug
The Native TimePicker component throws a console error when a value is passed to its steps property.

To Reproduce

  1. Open this StackBlitz example
  2. Click on the TimePicker to expand its popup
  3. Open the browser's console

Expected behavior
There shouldn't be any Javascript errors when working with the Timepicker

Screenshots
image

Completed
Last Updated: 04 Apr 2022 12:22 by ADMIN
Created by: jake
Comments: 0
Category: TimePicker
Type: Bug Report
1

Describe the bug
There are issues with the selection of the "min" and "max" values of the TimePicker when such are selected for the component.

  • The 'min' value cannot be the first selection the user makes after the initialization of the component. If the user opens the TimePicker's popup, the min value is selected by default. If one clicks on the "Set" button the min value should be selected but instead, the value is 12:00 AM.
    If the user selects a value different from the min, and then tries to select the min, the minimum value is correctly selected.
  • The max value is correctly selected but the component treats it as an invalid value.

To Reproduce

  1. Open this StackBlitz example
  2. To test the min value issue open the TimePicker and click on the "Set" button
  3. To test the max value issue, open the TimePicker and select 10:15 PM in the popup

Expected behavior
Both the min and max values defined for the component should be selectable and valid values in all use-case scenarios of the TimePicker.

Completed
Last Updated: 04 Apr 2022 07:27 by ADMIN

Describe the bug
The TimePicker with custom inputs is working correctly until we use the Tab button to switch from one input to another. When the Tab button is pressed, an error appears in the console and breaks the application.

To Reproduce

  1. Open this StackBlitz example
  2. Focus the first input inside the component
  3. Press the Tab button

Expected behavior
The focus should be changed to the second input

Screenshots
image

Completed
Last Updated: 29 Mar 2022 04:11 by ADMIN

Describe the bug
The data inside the Chart is not updating when we change the data it is bound to.

To Reproduce
Steps to reproduce the behavior:

  1. Download this project(_re-render.zip) and install the NPM packages(run: npm i)
  2. Start the project(run: npm run serve)
  3. Click on the "Change dataset" button

Expected behavior
With each click of the "Change dataset" button, the "Duration" property of the first element inside the "projects" array is being changed. With this change of "Duration", the Chart should be updated.

Completed
Last Updated: 28 Mar 2022 15:14 by ADMIN

Describe the bug
With version 3.0.4 of the Grid component, there is a regression in the way the component displays date fields.
Till version 3.0.3, date fields defined like '2021-05-13T00:00:00' were correctly displayed. From version 3.0.4 fields defined as '2021-05-13T00:00:00' are not displayed in the Grid.

To Reproduce
Steps to reproduce the behavior:

  1. Open this StackBlitz example
  2. See the 1st and 3rd row in the Date column

Expected behavior
All dates in the Date column should be visible as in this StackBlitz example.

Completed
Last Updated: 02 Mar 2022 08:30 by ADMIN
Created by: Shashwat
Comments: 2
Category: Popup
Type: Bug Report
0

https://github.com/zdravkov/kendo-popup-with-vite
Followed the below steps:
node - 16.13.1
pnpm install
Change App.vue as mentioned below
pnpm dev (works)
pnpm build (fails with type errors)

Type errors:
c:\temp\kendo-popup-with-vite>pnpm build

kendo-popup-with-vite@0.0.0 build c:\temp\kendo-popup-with-vite
vue-tsc --noEmit && vite build

node_modules/.pnpm/@progress+kendo-vue-popup@2.7.1_acc43b21ea211aeeda51cec780f114cb/node_modules/@progress/kendo-vue-popup/dist/npm/Popup.d.ts:2:57 - error TS2307: Cannot find module 'vue/types/options' or its corresponding type declarations.

2 import { RecordPropsDefinition, ComponentOptions } from 'vue/types/options';
~~~~~~~~~~~~~~~~~~~

node_modules/.pnpm/@progress+kendo-vue-popup@2.7.1_acc43b21ea211aeeda51cec780f114cb/node_modules/@progress/kendo-vue-popup/dist/npm/Popup.d.ts:63:72 - error TS2304: Cannot find name 'Vue'.

63 export interface PopupAll extends PopupMethods, PopupState, PopupData, Vue {
~~~

node_modules/.pnpm/@progress+kendo-vue-popup@2.7.1_acc43b21ea211aeeda51cec780f114cb/node_modules/@progress/kendo-vue-popup/dist/npm/Popup.d.ts:68:37 - error TS2304: Cannot find name 'Vue'.

68 declare let Popup: ComponentOptions<Vue, DefaultData, DefaultMethods, {}, RecordPropsDefinition>;
~~~

Found 3 errors.

 ELIFECYCLE  Command failed with exit code 2.

Completed
Last Updated: 09 Feb 2022 09:03 by ADMIN

Describe the bug
When using the DatePicker with custom inputs, if you define a value in a random input and press Tab, a JS error appears.

To Reproduce

  1. Open this demo
  2. Click on the first input inside the DatePicker's DateInput
  3. Press Tab

Expected behavior
The cursor should move to the next input

Completed
Last Updated: 09 Feb 2022 08:51 by ADMIN

Describe the bug
The "keyup" event is triggered two times

To Reproduce

  1. Open this StackBlitz example
  2. Click on the Input
  3. Press enter and check the browser's console

Expected behavior
The event should be triggered once per button press.

1 2 3