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

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
Unplanned
Last Updated: 23 Feb 2022 12:51 by ADMIN
Created by: shieldsjared
Comments: 1
Type: Bug Report
0

Looking at the JSDoc for for `toDataSourceRequestString` and `toDataSourceRequest`, they both appear to have JSDoc above them, showing the parameter as:

 * @param {DataRequestState} state - The state that will be serialized.

Should this actually have `@param {DataSourceRequestState}`?

Unplanned
Last Updated: 02 Feb 2022 14:28 by ADMIN

Issue #1

Given:

Controlled TextaArea componenet with autoSize and rows properties.

const App = () => {
  const [state, setState] = useState();

  return (
    <TextArea
      value={state}
      onChange={(e) => setState(e.value)}
      autoSize={true}
      rows={2}
    />
  );
};

When:

Add couple text lines to extend TextArea size and remove these empty lines in any way

Then:

Content from TextArea field is removed but TextArea height stays the same, doesn't come back to it's initial value. It's different comparing to example from your docs where example contains uncontrolled component.


Issue #2

Given:

Controlled TextaArea componenet with autoSize and rows properties.

const App = () => {
  const [state, setState] = useState();

  return (
    <TextArea
      value={state}
      onChange={(e) => setState(e.value)}
      autoSize={true}
      rows={4}
    />
  );
};

and styles like these

.k-textarea textarea {
  border: 1px solid blue;
}

When:

Start typing anything

Then:

Height of textarea component is decreasing

Unplanned
Last Updated: 14 Jan 2022 13:03 by ADMIN

here is a quick repro: https://stackblitz.com/edit/react-dfwz3q?file=package.json

in package.json just switch @progress/kendo-react-grid from 4.10.0 back to 4.9.0 and the column menu renders.

bug still present up through 4.11, 4.12, and @latest 4.13

Unplanned
Last Updated: 07 Jan 2022 12:17 by ADMIN

Actual results:

aria-label is not defined for ‘Reply editor’ when the keyboard focus is on 'Reply’ edit box narrator is announcing as “Editing End of line”.


Expected 
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. Learn more by reading about the accessible name property. 


User Impact 
When interactive elements have an incorrect name, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content.  

Unplanned
Last Updated: 07 Jan 2022 11:24 by ADMIN
Repro-Steps:
  1. open the given URL using valid credentials.
  2. Navigate to 'Reply' button and invoke it.
  3. Navigate to 'insert image' button and invoke it.
  4. Now, try to upload the image and observe

Actual Result:

User is unable to navigate to 'upload' button in 'insert image' dialogue. On invoking 'insert image' dialogue focus is navigating in the background and after navigating whole page then focus is going to the 'insert image' dialogue. Now, when user try to upload the image, focus is going out of the dialogue (going to the top of the page).

 

Expected Result:

Focus order should follow the meaningful reading order of the page and should return to previous elements when exiting a control.
On invoking 'insert image' dialogue, focus should be on the 'close' button of the dialogue and it should not navigate in the background.
While trying to upload the image, focus should go to 'clear selected files, upload and insert' buttons to upload the image.


User Impact:

When focus order does not follow the visible reading order, the experience can create a different interaction pattern, and/or unintended content relationships for assistive technology users. On rare occasions, there is a logical reason the focus order is different from the reading order, but the meaning of the content and interactions must remain the same. 


Unplanned
Last Updated: 07 Jan 2022 11:22 by ADMIN

Actual Result:

Given I have a conteneditable div component in my web application, when I run FastPass using Accessibility Insights for Web, I get the follow error message:

 

Snippet
<div aria-label="Post a question or answer" contenteditable="true" class="ProseMirror"><p data-prewrap="true"><br></p></div>
How to fix
Fix the following:
ARIA attribute cannot be used, add a role attribute or use a different element: aria-label

Expected behavior

Given I have a conteneditable div component in my web application, when I run FastPass using Accessibility Insights for Web, then I should not receive the following error message above

Unplanned
Last Updated: 07 Jan 2022 11:16 by ADMIN

Looking at the deliver1.PNG, there is a grid with a 'MultiColumnComboBox' component inside one of the columns. When a name is removed from a role in one row (deliver2.PNG), then that row is deleted/removed, the row below it moves up but loses its name on the UI but the data is not effected (deliver3.PNG).

Can confirm all data is intact when passing information to the 'MultiColumnComboBox' component, it's just a UI bug which doesn't display the value that was selected in the unedited/deleted row. Can also confirm this bug exists in other grids with 'MultiColumnComboBox' components.

The code path is as follows in images code1.PNG, code2.PNG, and code3.PNG. It can be seen there is a UserComboBoxCell element which returns a component called 'EditableGridMultiColumnComboBoxCell'. It is this component that uses the the 'MultiColumnComboBox' component.

Unplanned
Last Updated: 26 Oct 2021 12:46 by ADMIN
Actual:
Narrator is being mute while navigating through the menu items present in combo box. Here keyboard focus and narrator focus are not in sync while navigating through them.

Expected:

Narrator shouldn't be mute , keyboard focus and narrator focus should be in sync and narrator should announce the info about the menu items clearly


User Impact:

Users with visual impairment who rely on screen readers will face difficulties if narrator is not announcing any information about the menu items present in combo box while navigating through them.

Unplanned
Last Updated: 23 Sep 2021 12:56 by ADMIN
Created by: Nilton
Comments: 1
Type: Bug Report
0

When a user focus an empty DatePicker input using tab, the caret starts at the end (right side) of the input.

We need it to start at the left side, so the user can type without having to go all the way back to the left.

Unplanned
Last Updated: 13 Sep 2021 07:53 by ADMIN

Hi Team, 

###Current Behavior

When displaying checkboxes, they are not aligned for nodes with children vs. nodes without children

 

### Example

https://stackblitz.com/edit/react-rqvush?file=app/main.jsx

 

### Expected Behaviour

Nodes checkboxes should be aligned the same regardless of if they have children.

 

###Version

4.8.0

 

Thanks and Kind Regards,
Grant

Unplanned
Last Updated: 06 Aug 2021 10:08 by ADMIN
Pre-requisite:
Add accessibility insights for web extension for edge Anaheim(Dev) browser from https://accessibilityinsights.io/

Repro-Steps:
  1. open the https://answers.microsoft.com/en-us/msoffice/ using valid credentials.
  2. Select 'reply' button.
  3. Navigate to 'Insert image' button and invoke it.
  4. Now Run the fast pass using Accessibility Insights for web and observe the failure 'label'.

Actual results:

Aria label attribute is not defined for button in 'Insert image' dialogue.

Narrator is announcing as 'No file chosen, choose file, button'.


Expected results:

Aria label attribute should be defined for button in 'Insert image' dialogue.

 

User Impact:

Adding effective form labels is absolutely necessary to make forms accessible. The purpose of form elements such as a checkboxes, radio buttons, input fields, etc. is often clear for sighted users, even if the form element is not programmatically labeled. This isn't usually the case for screen reader users. Adding a label to all form elements eliminates ambiguity and contributes to a more accessible product.

Unplanned
Last Updated: 06 Aug 2021 10:08 by ADMIN
Pre-requisite:
Add accessibility insights for web extension for edge Anaheim(Dev) browser from https://accessibilityinsights.io/

Repro-Steps:
  1. open the given URL using valid credentials.
  2. Navigate to 'Reply' button and invoke it.
  3. Navigate to 'Insert image' button and invoke it.
  4. Now Run the fast pass using Accessibility Insights for web and observe the failure 'Nested- interactive'.

Actual results:

Nested interactive controls are not announced by screen readers


Expected results:

Interactive control elements have focusable descendants.

 

User Impact:

When interactive elements have an incorrect name and role, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content. Knowing the role for a control helps users know what will happen when that object has focus and is selected, as well as what keyboard shortcuts to use when interacting with the control.  

Unplanned
Last Updated: 06 Aug 2021 10:06 by ADMIN
Created by: Kavitha
Comments: 1
Type: Bug Report
0
Repro-Steps:
  1. open answers.microsoft.com/en-us/msoffice/ using valid credentials.
  2. Navigate to any article link and hit enter.
  3. Select 'reply' button.
  4. Navigate to 'format' list and invoke it.
  5. Now Run the fast pass using Accessibility Insights for web and observe the failure 'aria input field name'.

Actual Result:
Aria input field doesn’t have an accessible name.

Control type is defined incorrectly as list item for combo box for 'format' combo box.

Expected Result:
Ensure every aria input field should have an accessible name.
Control type should be defined as combo box.

User Impact:
ARIA widget roles require additional attributes that describe the state of the widget. If a required attribute is not provided, the state of the widget will not be communicated to screen reader users.
Unplanned
Last Updated: 05 Aug 2021 05:43 by ADMIN
Repro-Steps:
  1. open the given URL using valid credentials.
  2. Navigate to 'Reply' button and invoke it.
  3. Navigate to 'color group' and invoke it.
  4. Now, Navigate to the colors in color group and listen to Narrator announcement.

Actual Result:

On navigating to colors, Narrator is staying mute and not announcing anything.

 

Expected 
On navigating to colors, Narrator should announce the name of the color.


User Impact 

When interactive elements have an incorrect name, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content. 

Unplanned
Last Updated: 05 Aug 2021 05:42 by ADMIN
Repro-Steps:
  1. open the given URL using valid credentials.
  2. Navigate to 'Reply' button and invoke it.
  3. Navigate to 'table' button and invoke it.
  4. Now, try to navigate to table cells to select the size of the table and observe

Actual Result:

After invoking 'table' button, user is unable to select the size of the table i.e, Keyboard focus is not going to 'Insert row and column cell components.

Tab index property is not defined.

 

Expected 
Control(s) must be accessible to 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 keypresses.  

User should be able to navigate to insert row and column cell components to select the size of the table.


User Impact 
When interactive components are not accessible, assistive technology users are blocked, which leads to everything from inaccessible content, features, and functionality, up to entire applications or sites. 

Unplanned
Last Updated: 28 Jul 2021 15:52 by ADMIN
Created by: Grzegorz
Comments: 1
Type: Bug Report
0

We have two issues with grid with virtual scroll.

Both are registered on github.

First one is really blocking us: https://github.com/telerik/kendo-react/issues/1010

Second one we found on Safari, it's also very critical for our customers: https://github.com/telerik/kendo-react/issues/1013

 

Version: 4.7.0. Please note that version specified in Additional information does not make sense as we use Kendo React not Kendo UI.

Can you help us somehow?

Unplanned
Last Updated: 19 Jul 2021 10:03 by ADMIN
Pre-requisite:
Add accessibility insights for web extension for edge Anaheim(Dev) browser from https://accessibilityinsights.io/

Repro-Steps:
  1. open the given URL using valid credentials.
  2. Select 'reply' button.
  3. Now Run the fast pass using Accessibility Insights for web and observe the failure aria required children.

Actual results:

Elements with Aria role is not containing child role with in them.


Expected results:

Elements with Aria role should contain child role with in them.

 

User Impact:

For each role, WAI-ARIA explicitly defines which child and parent roles are allowable and/or required. ARIA roles missing required child roles will not be able to perform the accessibility functions intended by the developer.


1 2