Unplanned
Last Updated: 19 Sep 2022 16:39 by ADMIN
Created by: Marcu
Comments: 1
Type: Bug Report
0

When I press on a day from the past the DatePicker automatically scrolls to the next/previous year. Please check the attached video. 

Is there any workaround for this issue ?

Unplanned
Last Updated: 01 Sep 2022 08:38 by ADMIN

Dear Kendo,

 

I'm currently working on a data grid that has virtual scrolling enabled. When a user is scrolling fairly quickly, the screen will constantly flash white. See video in attachment.

I see this same behaviour in the example provided in the docs here: https://stackblitz.com/run/?file=app%2Fmain.jsx although it is slightly less noticeable.

What can we do to fix this?

Thanks in advance.

Kind regards,

Peter

Need More Info
Last Updated: 29 Aug 2022 10:12 by ADMIN

Environment Details:
OS: Windows11 version 21H2 (OS build 22000.856)
Edge Browser version: 
104.0.1293.47

Repro steps:
1. Open Code Pen: https://codepen.io/m1mrt/pen/VwXjEzJ page in Edge Browser.2. Run Axe dev tools3. Observe an issue that select element has an accessible name.

Actual Result:Select element does not have an accessible name.

Expected Result:
All components need an accessible name, ideally using semantic elements and attributes. In rare cases, aria-label or aria-labelled by may be needed to alter the name.

Screenshot attachment:

Declined
Last Updated: 18 Aug 2022 12:28 by ADMIN

Test Environment:

OS: Windows_11
Version: 21H2
OS Build: 22000.795

Browser: Version 103.0.1264.71 (Official Build) (64-bit)

Prerequisite steps:

1. Go to system settings.

2. Navigate to 'Accessibility' and activate it.

3. Navigate to 'Contrast theme' and activate it.

4. Select 'Desert/Aquatic' High Contrast theme in the combo box.

 

Repro Steps:

1. Open given URL https://canvasjs.com/docs/charts/chart-options/axisx/viewport-minimum/ in Edge.

2. Graph page will be open. 

3. Turn on High contrast theme. 

4. Verify that Graphs are not adapting high contrast Aquatic and Desert modes or not. 

 

Actual Behavior:

Graphs are not adapting high contrast Aquatic and Desert modes. They remain same as in normal mode.  

 

Expected Behavior:

 Graphs should adapt high contrast Aquatic and Desert modes as defined. All elements should adapt to respective modes properly. 

Need More Info
Last Updated: 14 Aug 2022 12:07 by ADMIN

Test Environment:

OS: Windows_11
Version: 21H2
OS Build: 22000.795
Browser: Version 103.0.1264.71 (Official Build) (64-bit)

URL: https://agentcalendardevone.azurewebsites.net/SMBEntryForm.aspx?trg=testteam&campaign=Microsoft%20Internal%20Test%20Camapign

Screen Reader: NVDA (2021.3)

Repro Steps:

1. Open URL: SMB Scheduler (agentcalendardevone.azurewebsites.net) page in Edge Browser.

2. Provide valid 'Email address' in text field and activate 'Book New Appointment'.
3. Click on view Available Appointments.
4. Open NVDA.
5.Navigate and activate 'Calendar' icon where popup appears.
6.Naviagte to controls.

7. Observe an issue that Incorrect role 'link' is defined on button controls.

Actual Behavior:

Incorrect role 'link' is defined on button controls present on 'Calendar' popup.

Expected Behavior:

In this case, the expected role is {button}. All components need a proper role attribute, ideally with semantics. In rare cases a role attribute should be added to give full context and information to assistive technology. Learn more by reading about when to use an aria role and the html/aria role mappings.


Need More Info
Last Updated: 14 Aug 2022 12:06 by ADMIN
Created by: eDAD
Comments: 1
Type: Bug Report
0

Build Dates & Run Dates range picker don't highlight days

Pre-Requisites (if any)
1. Go to system settings.
2. Navigate to 'Accessibility' and activate it.
3. Navigate to 'Contrast theme' and activate it.
4. Select 'Desert/Aquatic' High Contrast theme in the combo box.

Repro-Steps:

1. Open URL PowerGates Graph in Edge Dev.
2. Navigate to Build Date dropdown button using tab key and activate it.
3. Navigate to the ‘Within range ’calendar picker button and activate it.
4. Observe that issue.

Actual Result:

The Build Dates & Run Dates range picker both don't highlight the currently selected date does not outline the current date, as it does without contrast. Occurs in both Aquatic (High Contrast Black) and Desert (High Contrast White) modes.

Expected Result:
The current selected date should be highlighted, and today's date should be outlined.

User Impact:
If any image, icon, hyperlink, text or visual focus disappear when high contrast mode is enabled, will make the UI confusing and difficult for users with low vision to navigate easily to the desired element.
Need More Info
Last Updated: 14 Aug 2022 12:04 by ADMIN
Created by: eDAD
Comments: 1
Type: Bug Report
0

Incorrect role as link is defined for header controls of 'Branches' table.

Repro-Steps:

1. Open given URL DiskSnapshotDiff Graph in Edge Dev.
2. Enable Narrator using 'Ctrl+ Win + Enter' key.
3. Navigate to header controls present on the 'Branches' table using Tab key.
4. Verify that incorrect role as link is defined for header controls of 'Branches' table or not.
Actual Result:
Incorrect role as link is defined for header controls of 'Branches' table.

It is functioning as a button. On activating the header control filter is activating.

Expected Result:
Correct role as 'Button' is defined for header controls of 'Branches' table.

User Impact:
Screen reader user will be impacted if incorrect role is defined. It will confuse screen reader user for its functionality.
Need More Info
Last Updated: 14 Aug 2022 12:02 by ADMIN
Created by: eDAD
Comments: 1
Type: Bug Report
0

After applying filter or page number, the table content gets changed but the screen reader didn't inform about the same.

Repro-Steps:

  1. Open the WPG - Home URL in browser.
  2. Now, navigate to table in table in scan mode.
  3. Observe the issue.

 

Actual Result:

After performing below action's, the table content gets changed but the narrator didn't announce about the content change:

  • After applying filter (any), if data shown as well as if no content found.
  • After selecting page no.

Expected Result:
The narrator should announce about change in the data table as soon as the filter applied, or page get changed.


User Impact:

Users who rely on screen readers are getting confused if the focus lands on the icon and only announces link without announcing the name of the link.
Need More Info
Last Updated: 14 Aug 2022 12:00 by ADMIN

Test Environment:

OS: Windows_11
Version: 21H2
OS Build: 22000.795
Browser: Version 103.0.1264.71 (Official Build) (64-bit)

URL: https://agentcalendardevone.azurewebsites.net/SMBEntryForm.aspx?trg=testteam&campaign=Microsoft%20Internal%20Test%20Camapign

Repro Steps:

'Month' control on 'Calendar' popup not accessible using keyboard.
1. Open URL: SMB Scheduler (agentcalendardevone.azurewebsites.netpage in Edge Browser.
 
2. Provide valid 'Email address' in text field and activate 'Book New Appointment'.
3. Select 'Appointment' tab in header.
4. Navigate and activate 'Calendar' icon where popup opens.
5. Try to navigate and activate 'Month' control.

6. Observe an issue that 'Month' control on 'Calendar' popup is not accessible using keyboard.

'Click to book' and header controls are not accessible using keyboard.

1. Open URL: SMB Scheduler (agentcalendardevone.azurewebsites.net) page in Edge Browser.

2. Provide valid 'Email address' in text field and activate 'Book New Appointment'.

3. Select any 'Time Zone' in dropdown and click 'View Available appointments' button.

4. Navigate to the table content.

5. Observe the issue that the controls in the table such as ("<", ">", "Today", calendar widget, "Week", "Click to the book") does not receive keyboard focus.

Actual Behavior:

'Month' Control on 'Calendar' popup is not accessible using keyboard.

Expected Behavior:

Control(s) must be accessible to Bluetooth keyboards and other assistive technology. Common causes of this problem include a) the element does not have a proper role assigned, b) the element needs tab-index="0" attribute to be focusable, or c) the component is not registering key presses.

 

Won't Fix
Last Updated: 09 Aug 2022 07:28 by ADMIN

StackBlitz example: https://stackblitz.com/edit/react-vg8pu5?file=app/main.jsx

 

If you have a Form <Field component={Input}> inside an <ExpansionPanel>, if you press space or enter within the input, the expansion panel also receives the key event and will expand/collapse. It seems like these key events should not bubble out of the Field component.

Won't Fix
Last Updated: 31 Jul 2022 07:23 by ADMIN

In the Checkbox onChange callback, event.nativeEvent.target.checked seems to be set differently depending on whether the input was toggled by mouse click or by pressing space.

After clicking on the Checkbox, event.value and event.nativeEvent.target.checked will have the same value, consistent with the Checkbox's new state.

After pressing space with the Checkbox focused, event.value and event.nativeEvent.target.checked will have different values, with event.value containing the Checkbox's new state and event.nativeEvent.target.checked containing the Checkbox's old state.

I would expect event.nativeEvent.target.checked to be set the same way regardless of whether I am toggling the Checkbox with mouse or keyboard.  Furthermore, I would expect event.value and event.nativeEvent.target.checked to always be equal to each other.

I made a code sandbox to demonstrate the bug here: https://codesandbox.io/s/kendo-react-checkbox-bug-26f7ur

Under Review
Last Updated: 30 Jul 2022 09:08 by ADMIN

We are currently passing a React.Node which contains both text and custom icons to the DropDownButton text property. The automatically generated aria-label of the DropDownButton returns [object Object] instead of any recognizable text.

Steps to Reproduce:

  • Create a DropDownButton with text property set to a React.Node - eg:
<DropDownButton text={<div>test text</div>}>
  • Inspect the DropDownButton aria-label value using the developer console

Expected Result:

aria-label contains the text inside the React.Node

aria-label="test text dropdownbutton"

Actual Result:

aria-label contains [object Object]

aria-label="[object Object] dropdownbutton"

 

Unplanned
Last Updated: 28 Jun 2022 12:01 by ADMIN
Created by: Daniel
Comments: 1
Type: Bug Report
2
Current Behaviour

When an item, which has submenu, from the menu dropdown is hovered the submenu appears. But if you click on the hovered item the submenu disappears.

Expected Behaviour

When an item, which has submenu, from the menu dropdown is hovered and then clicked the submenu should stay visible.

MInimal Reproduction

I'm providing a reproduction from Kendo React code examples.

https://stackblitz.com/edit/react-jqhjyv?file=index.js

Won't Fix
Last Updated: 22 Jun 2022 21:08 by ADMIN

When the listbox has many items (roughly 200 and growing) the item attribute makes the listbox act slow when you want to click the item.
Even if the item render only returns the same value as not setting the item attribute. It seems like all the items re-render when it gets clicked?

Also in this example https://www.telerik.com/kendo-react-ui/components/listbox/customization/ it is possible to drag and drop a custom item.
But this is not working when we copy exactly the same code from the example. The drag event gets triggered but nothing happens. 
Both lists have items to avoid this bug: https://github.com/telerik/kendo-react/issues/1300

I can post my source code but it is literally the same as the example. When we remove the item attribute the drag and drop works again. 

Unplanned
Last Updated: 10 Jun 2022 11:53 by ADMIN

Hello,

After updating the kendo version in my project to "^5.1.0" I've noticed that some errors are appearing in our console when we are trying to resize items in the Scheduler. 

"use-resize-item.js:53 Unable to preventDefault inside passive event listener invocation."

I have attached a video with the error.

Thanks!

Unplanned
Last Updated: 10 Jun 2022 08:39 by ADMIN
Scheduled for 5.4.0
Created by: Simonas
Comments: 1
Type: Bug Report
0
Setting react grid prop "scrollable" value to "none" and dragging column header causes a crash. https://stackblitz.com/edit/react-vpw68o?file=app/main.jsx
Under Review
Last Updated: 03 Jun 2022 07:23 by Tom

A little thing, but users remember position of UI elements more than anything else. The filter buttons on the grid by default are not in the same place though for all filter types.

It would be preferable if the filter buttons were all on the same side, regardless of the filter type (e.g., some types put it on the left, while others put it on the right). Pictures below for context.

 

 

Under Review
Last Updated: 25 May 2022 05:09 by ADMIN
Planned
Last Updated: 24 May 2022 14:15 by ADMIN
I've already submitted this to the GitHub issues - https://github.com/telerik/kendo-react/issues/1297

Submitting here as it is an important regression with React 18 breaking all popup animations.
Under Review
Last Updated: 20 May 2022 08:33 by ADMIN

In our unit tests, we sometimes want to be able to use the ByTestId methods of the React Testing Library to find bits of DOM created by a Kendo component.  However, setting a data-testid attribute (or really any data- attribute) on a Kendo component does not always result in the attribute appearing anywhere in the final DOM.

To demonstrate, below is a test suite (also included in the zip) where I tried putting a data-testid attribute on the Kendo components Input, TextArea, Checkbox, Slider, SliderLabel, MultiSelect, and DatePicker, then checked if the attribute appeared in the rendered DOM.  The tests for Input, TextArea, and Checkbox are successful.  The ones for Slider, SliderLabel, MultiSelect, and DatePicker are not.

import { render, screen } from '@testing-library/react';
import { Input, TextArea, Checkbox, Slider, SliderLabel } from '@progress/kendo-react-inputs';
import { MultiSelect } from '@progress/kendo-react-dropdowns';
import { DatePicker } from '@progress/kendo-react-dateinputs';

// SUCCEEDS
describe('Kendo Input', () => {
    it('supports data attributes', () => {
        render(
            <Input data-testid="the-input" />
        );

        const input = screen.queryByTestId('the-input');
        expect(input).toBeTruthy();
    });
});

// SUCCEEDS
describe('Kendo TextArea', () => {
    it('supports data attributes', () => {
        render(
            <TextArea data-testid="the-text-area" />
        );

        const textarea = screen.queryByTestId('the-text-area');
        expect(textarea).toBeTruthy();
    });
});

// SUCCEEDS
describe('Kendo Checkbox', () => {
    it('supports data attributes', () => {
        render(
            <Checkbox label={"Chad"} data-testid="the-checkbox" />
        );

        const checkbox = screen.queryByTestId('the-checkbox');
        expect(checkbox).toBeTruthy();
    });
});

// FAILS
describe('Kendo Slider & SliderLabel', () => {
    it('supports data attributes', () => {
        render(
            <Slider min={1} max={2} data-testid="slider-root">
                <SliderLabel position={1} data-testid="slider-label-1">One Fish</SliderLabel>
                <SliderLabel position={2} data-testid="slider-label-2">Two Fish</SliderLabel>
            </Slider>
        );

        const sliderRoot = screen.queryByTestId('slider-root');
        const sliderLabel1 = screen.queryByTestId('slider-label-1');
        const sliderLabel2 = screen.queryByTestId('slider-label-2');

        // test them all at once so we can know the full scope of our failure/success
        expect({
            sliderRoot,
            sliderLabel1,
            sliderLabel2
        }).toMatchObject({
            sliderRoot:   expect.anything(), // don't be null or undefined
            sliderLabel1: expect.anything(), // don't be null or undefined
            sliderLabel2: expect.anything()  // don't be null or undefined
        });
    });
});

// FAILS
describe('Kendo MultiSelect', () => {
    it('supports data attributes', () => {
        render(
            <MultiSelect data-testid="the-multi-select" />
        );

        const multiselect = screen.queryByTestId('the-multi-select');
        expect(multiselect).toBeTruthy();
    });
});

// FAILS
describe('Kendo DatePicker', () => {
    it('supports data attributes', () => {
        render(
            <DatePicker data-testid="the-date-picker" />
        );

        const datepicker = screen.queryByTestId('the-date-picker');
        expect(datepicker).toBeTruthy();
    });
});
While it is theoretically possible the problem is limited to just Slider, SliderLabel, MultiSelect, and DatePicker, I highly doubt it.
1 2 3 4 5 6