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. 


Under Review
Last Updated: 19 Jul 2021 11:39 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: 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.


Under Review
Last Updated: 13 Jul 2021 06:00 by ADMIN

Actual Result:

While navigating in table, Narrator is not announcing as 'enter table' and it is also not announcing rows and column information. while navigating in table, With arrow keys or table navigation keys or tab key, Narrator is announcing as 'end of line/blank'.

With caps-arrow keys, Narrator is giving row and column information.

 

Expected 
While navigating in table, Narrator should announce as enter table and it should also give row and column information. And while navigating with arrow keys or table navigation keys or tab key, Narrator should not announce as 'end of line/blank' instead it should give row or column information


User Impact 
Visually impaired users who rely on screen reader will face difficulties to determining Row/Column information of a cell.
Completed
Last Updated: 09 Jul 2021 11:19 by ADMIN

Hello,

I am using tooltip component for a long desciption field in my grid cell. And I am using it as it will encapsulate Grid component (like the example below) as it is suggested in this page.

<Tooltip openDelay={100} position="right" anchorElement="element"> <Grid>... </Grid> </Tooltip>

My grid has a date field and I am using columnMenu for filtering (GridColumnMenuFilter). An error occurs when I hover the text of date field and says : 

Tooltip(...): Nothing was returned from render. This usually means a return statement is missing. Or, to render nothing, return null.

I also trid to replicate the problem in the example on this page and it gives the same error. I forked the project and you can check it from https://react-ed5jns.stackblitz.io/

Simply move the cursor over month/day/year in a date filter area and see the problem. This seems like a bug. Or if there is any solution to this, I would like to see a workaround.

 

 

Thanks

 

Completed
Last Updated: 16 Jun 2021 11:22 by ADMIN

if (_this.element && document.activeElement === _this.element) {
                _this.element.setSelectionRange(selection.start, selection.end);
            }

@progress/kendo-react-dateinputs": "^4.3.0"

DatePicker and DateInput React components malfunction when rendered inside iFrame.

 

For example, key navigation between date parts is not working for the DateInput/DatePicker rendered inside iFrame.

When user clicks on the month part of the date, the month part does not get selected.

Same for day or year part.

 

The reason is a code similar to this in DateInput.js:

 

if (_this.element && document.activeElement === _this.element) {
                _this.element.setSelectionRange(selection.start, selection.end);
            }


if (document.activeElement !== _this.element) 

This code references the top level "document".

If the React component is rendered inside iFrame, we need to use the contentDocument of the iFrame to have this code working as expected.

 

Could replace "document" with "_this.element.ownerDocument" to make it work inside iFrame as well as in the top level window.

 

Now "document.activeElement" always returns the reference to the iFrame element rather than the expected date input element inside iFrame.

 

 

 

Completed
Last Updated: 04 Jun 2021 13:32 by ADMIN

Description of the problem

In the Grid component with infinite scrolling, when a user scrolls down, the grid will bounce them back up to the first row when loading the next couple of rows. We get this same behavior in our application so it doesn't seem to be a mistake in the demo. We've encountered this issue in both version 1.x and the most recent version of Kendo.

To reproduce:

  • go to the demo for this component;
  • slowly scroll down in the grid component.

Code, screenshots, etc

Since this is also broken in the docs, I don't think it's necessary to add screenshots or code.

Under Review
Last Updated: 24 May 2021 08:48 by ADMIN
The CSS styling of the Stepper component breaks when there is only 1 step defined. It may sound weird to only have 1 step but the items prop is an array and therefor should support 1 single step. Currently when only 1 step is defined the stepper bar extends like it's going to a 2nd step but just stops. It'd be nice if visually that progress bar just didn't show up if there was no 2nd step.
Completed
Last Updated: 24 May 2021 07:58 by ADMIN

It's annoying because:

 

1) Every time I go to a new page or refresh my browser it comes up bright yellow

2) It blocks the search bar which I use a lot

3) The seminar is over which just annoys me more

 

I'm OK if you want to tell me once like a privacy notice, but don't tell me every time my web page refreshes and overwrite part of the page.

 

 

1 2 3 4