Hi,

Not sure what the preferred way to report a problem is. I have posted it on GitHub as well:
https://github.com/telerik/kendo-react/issues/1519

Could someone help me out with this issue?

Thank you in advance.

Request to have the sliderbar have different colors. It is for user experince, knowing that the slider is going either to the sucess or fail.

Currently, there is a following signature of function "rowRender" passed to React Grid:

rowRender?: (row: React.ReactElement<HTMLTableRowElement>, props: GridRowProps) => React.ReactNode;

I managed to access something which I assume represents this index somehow by using "row._owner.index" although I'm not completely sure if that is always identical to the index of the row being rendered.

It would be very helpful if an index of a rendered row could be accessed as follows:

rowRender?: (row: React.ReactElement<HTMLTableRowElement>, props: GridRowProps, index: number) => React.ReactNode;

Hi

Would it be possible to add an option/prop to the KendoReact spreadsheet component to make the whole workbook or specific sheets read-only, instead of specifying cell ranges?

This would make it easier when users need to view a file/spreadsheet without editing it.

Thanks

Integrated tooltip to react data grid, but when I drag & drop column header to group it by column, It displays the tooltip text instead of column field title

Hi, 

I'm working on a grid which has an action cell with buttons, which of course i dont want to export, but when i try to pass a custom column configuration to the export it fallbacks to the grid's one.

I made further investigation on the kendo-react-private repository and i found out that effectively there's a preference for the grid columns rather than custom

more precisely on kendo-react-private>packages>excel>src>ExcelExport.tsx (line 201~206)

const columns = this.extractColumns(
            gridColumns ||
            externalColumns ||
            this.props.columns ||
            React.Children.toArray(children)
        );

this is the piece of code i was talking about.

as you can see if gridColumns has a value is preferred rather than externalColumns

it would be nice to have a property onto the grid column definition stating if that column should be exported or not (best case)

or just preferring externalColumns to gridColumns (base case)

Title:
[Answers Community: Ask a question]: Unable to navigate and access the 'Remove' button using keyboard.

Test Environment:
Windows 11 OS version:22H2 22621.1992
Edge Version 114.0.1823.82(Official build) (64-Bit)

Repro-Steps:
1.  Open https://www.telerik.com/kendo-react-ui/components/upload/url.
2.  Navigate to 'select files..' button using arrow key and invoke it using enter key.
3.  Upload any file.
4.  Now try to navigate using tab key and access 'Remove' button using keyboard and check whether its accessible or not using keyboard.

Actual Result:
Unable to navigate and access the 'Remove' Button using keyboard.


Expected Result:
User should be able to navigate and access the 'Remove' button using keyboard.

User Impact:
User with motor impairments who rely on keyboard will not be able to access 'Remove' button if user is not able to navigate to the button using keyboard.

Hi team, 

Im my example (see here), I've added a 'name' attribute to the 'Persons' resource data, and changed the textField mapping to use the 'name' field, however the scheduler is still displaying the results of the 'text' attribute. 

Leading me to think that the scheduler is hardcoded to only look for the text attribute, because if its changed/removed, the scheudler does not display anything, regardless of what the 'textField' value is.

Please advise.

Thanks,
Grant

Environment (OS, Application, Versions)

Repro Steps

1. Open URL: Column Menu - Kendo React (telerik.com)
2. Navigate to context menu controls available on column headers of Basic usage table.
3. Verify if context menu is accessible using keyboard.

Actual Results

The 'context menu' controls available on the column headers under the basic usage table are not accessible using the keyboard.

Expected Results

The 'context menu' controls available on the column headers under the basic usage table should be accessible using the keyboard.

Hi, I am Lavanya!

in my dropdown list, there are horizontal layouts I need to change to the vertical dropdown list

and also I have attached bar data in that I need to make a dropdown filter of the month how can I use that

Current Behaviour

When I lock columns In data grid with resizable columns - for example 1st and 3th and resize the 1st one - after we scroll horizontally the 3th column goes on top of the 1st column. This happens when we haven't set a width prop.

Expected Behaviour

Resized columns not overflowing on each other when scrolling horizontally and don't have width prop.

MInimal Reproduction

I'm providing a reproduction from Kendo React code examples.
https://stackblitz.com/edit/react-xvxy59?file=app%2Fmain.jsx

I have attached files, in which there is an app bar content there is a dropdown in the dropdown there are four elements, in that I need four drawer container on the left side as I attached by clicking the single dropdown, how can I attach 4 drawer container in a single project 

Thank you

Currently the React DateRangePicker component shows its calendar popup any time either of the date text inputs are focused.

It would be nice to have more control over this behavior buy providing a prop to customize what actions open the popup.

Our use case is that currently the DateRangePicker (as of v5.11.0) cannot be used to make a 508 accessibility compliant site (reference support ticket 1597095  : which IMO is a bug, but trying to also find a workaround that we can roll out quickly) due to the way the popup breaks tab order in the browser. If keyboard users could tab into the Start/End inputs without the popup opening, then they could type in a date and tab to the next control (currently they cannot because the popup breaks tab order). A mouse user clicking into the input would be fine to see the popup. So having a prop to specify the auto-open should happen in click, not on focus, with a keyboard shortcut to open the popup if they want it (which already exists as alt+down), would be an easy workaround to get us back into 508 compliance.

I could imagine such a pop to control auto-open of the calendar popup to take one of 3 values; 'focus' (same behavior as current) 'click' (open on click, but not on keyboard focus) 'none' (no auto open. user can press alt+down to open).

Hi,

If you use kendo-theme-bootstrap for most Kendo React inputs, it results in bootstrap styling being applied to the input e.g. https://www.telerik.com/kendo-react-ui/components/dateinputs/datepicker/ or https://www.telerik.com/kendo-react-ui/components/dropdowns/combobox/. With the Bootstrap theme selected the DatePicker and Combobox have blue shadows on focus.

This is not true for the DropDrownList: https://www.telerik.com/kendo-react-ui/components/dropdowns/dropdownlist/. The border on focus does not match Bootstrap styling.

Kind regards,

David

Hi,

Please see the following example of the dropdownlist with bootstrap theme applied:

https://stackblitz.com/edit/react-ejxe44?file=index.html

I have updated the bootstrap cdn to latest. Notice that bootstrap styling is applied to the dropdowns including focus shadowing.

Now please see the exact same example but with theme customisation using a custom scss file:

https://stackblitz.com/edit/react-tuq49c-g6ofwn?file=index.scss

Notice that bootstrap styling is no longer applied to the dropdowns, which do not have focus shadowing.

Kind regards,

David