Hi, when using the Kendo React Typography component like following:
<Typograpy.h1></Typograpy.h1>
compiler gives the following warning:
Imported JSX component h6 must be in PascalCase or SCREAMING_SNAKE_CASE react/jsx-pascal-case
We have problems with the grid because for no reason a 'display:none' appears, specifically in this creation action
We can't understand when the error might occur, we think it's a coincidence of class names.
Can you guide us through this error?
It is my first time raising a support contact so I don't know what background they can mostly support.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.
Environment (OS, Application, Versions)
Repro Steps
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 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
Hello? I want to set up drag and drop events from a grid's data to a treeview in React. I used to implement this with Kendo jQuery, but it seems that React doesn't provide this functionality.
Hello,
We have recently upgraded our packages to version: "@progress/kendo-react-grid": "^6.1.0". While testing the new look and feel of the application we've noticed that the pagination is no longer working on several grids from the application. After investigating for a while, we have found the property that is causing the issue(rowHeight), please take a look at the Stackblitz example from below.
https://stackblitz.com/edit/react-wwzkjy?file=app%2Fmain.tsx
As you can see, in the example the pagination is not working. If we remove the property "rowHeight" from the grid the pagination is working again. We are not sure how these two are related but can you tell us what is going wrong and how we can fix it?
Thanks!
In the kendo-react-data-tools component, we want to introduce the Autocomplete behavior in Fields.
For example, in the https://www.telerik.com/kendo-react-ui/components/datatools/ link, only 3 fields ( like Name, Price and Discontinued ) were used.
In our application, we have more than 100 fields and the user has to scroll all the way down to pick the required field for applying the filter.
This is a bug on your documentation website.
Go to https://www.telerik.com/kendo-react-ui/components/grid/ for example to see that the side panel on the left is empty in an Edge browser. It flickers then it disappears.
It works fin in Chrome and Firefox.
Environment (OS, Application, Versions):
OS Version: 22H2 (OS Build 25352.1)
Edge Dev: Version 121.0.2277.112 (Official build) (64-bit)
Repro Steps:
1. Open https://codepen.io/oneID/pen/LYaGREP and turn on NVDA.
2.Navigate to Populate grid and activate it using enter key.
3.Navigate to Expand button under domain in export to excel table.
4.Verify if the accessible name and role for the expand button is correct or not.
Actual Results:
Accessible name for the 'expand' button is not correct, Expand button is defined as link.
Expected Results:
Accessible name of 'expand' button should be sufficient for screen reader user. Accessible name should contain value available in domain as well.
Role should be defined as 'Button' as its behaving as button.
Hello,
We are encountering an issue with duplicate entries in our Kendo Grid with drag & drop functionality. When the grid is scrolled, clicking on any of the header cells multiple times results in the first entry being duplicated. This problem occurs on the example provided on your website as well: Kendo React Grid Row Reordering
Reproduction Steps:
You will notice that the first entry is duplicated multiple times. It appears that the reorder logic is being triggered when a header cell is pressed.
We are using version 6.1.0. Please refer to the attached video for a visual representation of the issue.
Thank you for your assistance.