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.

Planned
Last Updated: 25 Oct 2021 11:01 by ADMIN
Created by: Grant
Comments: 3
Type: Bug Report
0

Hi team, 

Im not sure if this is a bug or an incomplete feature, so please advise.

1) TabStrip / Window behavior in v4.8.0 with bootstrap theme 4.40.0, see https://stackblitz.com/edit/react-wdzeyo?file=index.html
Please note the style and behaviour of the window, its above the modal and can be dragged anywhere on the screen, even though it was rendered from within the TabStripTab component

2) TabStrip / Window behavior in v4.9.0 with bootstrap theme 4.42.0, see https://stackblitz.com/edit/react-zhkfdp?file=app%2Fmain.jsx
As you can immediately see in this example, the TabStripTab heading is also above the modal, an obvious bug
My concerns are around how the window can no longer be dragged outside the TabStripTab container. Is this by design, beacuse in my use case, my tabs are smaller than my windows.

Note: I have not tested the windows with any other components.

Please advise.

Many Thanks,
Grant

Under Review
Last Updated: 25 Oct 2021 08:15 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.

Completed
Last Updated: 19 Oct 2021 11:59 by ADMIN

Hi Team,

I would like to report the following Major bug for KendoReact v4.9.0:

Duplicate:
1) Open the Datepicker Demo page
2) Open any of the datepickers and click the month name, as you will see a few months are hidden on the right had side.
  The same behaviour continues if you click the year or decade.

Thanks and kind regards,

Grant

PS. This feedback form only allows me to select a "KendoUI for jQuery" version number.

Declined
Last Updated: 15 Oct 2021 05:18 by ADMIN

Repro:

  1. Create a DateTimePicker.
  2. Use its value prop to programmatically control the value the control uses.
  3. Add clickable Button (or other means) to programmatically set the value to an invalid date (i.e. something like new Date("invalid!").
  4. Click the Button.  The date displayed becomes "NaN/NaN/NaN 12:NaN PM".  I suppose this is reasonable.
  5. Now, click the calendar popup icon on the right-hand side of the component.

Expected:

Displays a calendar popup, perhaps defaulting to the current date & time.

Actual:

Throws an exception visible in the JavaScript console.  Replaces the UI with an error message.

Proof-of-Concept:

https://stackblitz.com/edit/react-gvipiu?file=app%2Fmain.tsx


import * as React from 'react';
import * as ReactDOM from 'react-dom';

import {
  DateTimePicker,
  DateTimePickerChangeEvent,
} from '@progress/kendo-react-dateinputs';
import { Button } from '@progress/kendo-react-buttons';

const App = () => {
  const [date, setDate] = React.useState(new Date());

  const handleChange = (event: DateTimePickerChangeEvent) => {
    setDate(event.value);
  };

  const handleClick = () => {
    setDate(new Date('invaild!'));
  };

  return (
    <React.Fragment>
      <div className="example-wrapper">
        <p>
          (use Alt+<code>↓</code> to open the date-time selector, <code>←</code>{' '}
          and <code>→</code> to navigate, <code>↑</code> to increment and{' '}
          <code>↓</code> to decrement the value)
        </p>
        <DateTimePicker onChange={handleChange} value={date} />
      </div>
      <Button onClick={handleClick}>
        Click me, then the calendar, to break the DateTimePicker.
      </Button>
      <div>{date?.toString()}</div>
    </React.Fragment>
  );
};

ReactDOM.render(<App />, document.querySelector('my-app'));
Important note: This POC code uses version 4.9.0 of kendo-react-buttons.  I do not know what that translates to in terms of the "version" dropdown.  I can't tell if "2021.1.119" is applicable here.
Planned
Last Updated: 01 Oct 2021 07:26 by ADMIN

toODataString throw exception on text filter changed from is null to contains. 

https://stackblitz.com/edit/react-ertg4z?file=app%2Fmain.jsx 

Repro step:

1. Choose filter by Name which is using text filter.

2. Change filter from Is null to contains.

3. toODataString threw exception.

 

Error in /turbo_modules/@progress/kendo-data-query@1.5.5/dist/cdn/main.js (1:7873)
Cannot read properties of undefined (reading 'replace')
Under Review
Last Updated: 28 Sep 2021 08:33 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: 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

Declined
Last Updated: 26 Aug 2021 10:44 by ADMIN

Hi Team, 

I have found an issue in the Grid Component that I think needs some attention, see below.,

## Current behavior
My GridColumns are not styling correctly when i hide/show them based on an edit state (for example). Some that have no width restrictions will the shortened then not lengthed.

 

## Current Version

KendoReact 4.8.0

 

## Expected behavior
If I hide/show a GridColumn, its width should not affect other GridColumns, only the Grid overall.

 

## Minimal reproduction of the problem with instructions
Example: https://stackblitz.com/edit/react-ngpvuj?file=app%2Fmain.jsx

Instructions:
1. View how age is the only column visible with a width attr
2. Click "Switch Mode" and notice how 'Id' is not added, but a width of 80 is now applied to the 'lastname' column, the same width as age
3. Click "Switch Mode" back to view, and see how id is removed and a width of 60 is applied to the 'firstname' column.

 

## Investigation:
Some investigation in the DOPM revealed that the issue is centred around the <colgroup> of the Grid's <table>:
- step 2 does the following to the <col>s in the <colgroup>
  - add a new col to the beginning with a width, for the Id column
  - add a new col to the end with a width, for the Age column
  - DOES NOT clear the width of the col group that used to be the age column

- step 3
 - Simply removes the last <col> in the group. Does not affect hte attributes of the remaining <col>s

 

I hope this was informative and can be resolved soon.

Kind Regards,
Grant

Declined
Last Updated: 06 Aug 2021 10:23 by ADMIN
  1. Open the https://answers.microsoft.com/en-us/msoffice/ using valid credentials.
  2. open any related article.
  3. Navigate to 'Reply' button and invoke it.
  4. Navigate to 'ordered list' button and invoke it.
  5. Navigate to the edit region and type some ordered list items.
  6. Now, Navigate to the ordered list items and listen to Narrator announcement.

Actual Result:

On navigating to ordered list items with arrow keys, Narrator is only announcing first letters of the text and while navigating with 'caps-arrow' keys, Narrator is only announcing position details of the list items.

Note: this issue is not observed with nvda

Nvda version: 2020.2

 

Expected 
On navigating to ordered list items with 'arrow keys' or using 'caps-arrow' keys, Narrator should announce the whole text of the list item including position details.


User Impact 
Knowing how many items are in a list is extremely useful to assistive technology users as they can know if they should attempt to skip the list, navigate to the end, help them recall placement of certain items, or orient themselves within the list.  

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?

Completed
Last Updated: 27 Jul 2021 07:43 by ADMIN

The ListView component has an item prop that allows you to specify the render component. That component receives ListViewItemProps. The ListViewItemProps type is not exported and cannot be properly imported elsewhere.

Under Review
Last Updated: 20 Jul 2021 04:55 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. 


1 2 3 4 5