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,
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!
Test Environment:
We use the PopOver component to create a menu that is more then just a list of links (i.e. a Jumbo Navigation including images, etc.).
Unfortunately the PopOver has no built-in functionality to automatically close it when the user clicks outside of the PopOver, so this has to be implemented manually.
So the request is to add a parameter to the PopOver component that allows to automatically close the popover when the user clicks outside of it when it's open.
Hello,
We've been using StockChart with Navigator to display a count trend. However, we have an accessibility bug reported on using that component due to single pointer options alternative is not provided for adjusting the graph points. Currently user can only achieve that through dragging. Do we support props that will display input box to resolve this accessibility issue?
MAS reference: https://aka.ms/MAS2.5.7
Dear sir/madam,
We noticed an error when setting the "defaultShowWorkHours" to false, it still shows the work hours as the default.
Check the Codesandbox
Expected behavior when you set "defaultShowWorkHours" to false, it shows the full day timeline
I'd like to turn off even/odd row highlighting for the Grid and use cell border instead.
I can do it by learning kendo css classes and override particular properties for certain classes but... I have many different vendors for different components and it's so a pitty to learn all the css classes hell...
It'd be supper cool to have something like turnOffAlternation/alternatingRows and showCellBorder/showBorders attributes on the Grid.
Hi, Keyboard navigation using "page down" and "page up keys" doesn't work.
Here is a stackblitz where the problem can be reproduced: https://stackblitz.com/edit/react-q9n5fe?file=app%2Fmain.tsx
Reproduction steps:
It only works when:
Best Regards
Hubert
Hi Team,
For MenuItem target="_blank" feature is not there. Please enable the same. which will be helpful as menu is the face of app.
Regards,
Revanth
Hi,
I would like to be able to specify a Grid Column template for the data without having to replicate the entire cell and its properties. Please see below for justification:
Consider the following example of KendoReact Grid Cell customisation: https://www.telerik.com/kendo-react-ui/components/grid/styling/#toc-adding-custom-cells
Following this approach results in the loss of a lot of properties from the grid cell compared with 'default' cells e.g.
<td colspan="1" class="" role="gridcell" aria-colindex="1" aria-selected="false" data-grid-col-index="0">Chai</td>
<td style="background-color: rgba(55, 180, 0, 0.32);">18 <span class="k-icon k-i-sort-asc-sm"></span></td>
These properties are important for many reasons including accessibility. There is another example of KendoReact Grid Cell customisation that preserves these properties here: https://www.telerik.com/kendo-react-ui/components/grid/cells/#toc-customization
e.g.
<td colspan="1" class="" role="gridcell" aria-colindex="4" aria-selected="false" data-grid-col-index="3">39</td>
<td colspan="1" role="gridcell" aria-colindex="5" aria-selected="false" data-grid-col-index="4" style="color: red;">false</td>
However, there is a considerable amount of code required to achieve this:
const CustomCell = (props) => {
const field = props.field || "";
const value = props.dataItem[field];
const navigationAttributes = useTableKeyboardNavigation(props.id);
return (
<td
style={{
color: value ? props.myProp[0].color : props.myProp[1].color,
}}
colSpan={props.colSpan}
role={"gridcell"}
aria-colindex={props.ariaColumnIndex}
aria-selected={props.isSelected}
{...{
[GRID_COL_INDEX_ATTRIBUTE]: props.columnIndex,
}}
{...navigationAttributes}
>
{value === null ? "" : props.dataItem[field].toString()}
</td>
);
};
I would like to be able to define a template for a cell without having to specify these properties every time.
Kind regards,
David
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.
Hi
Please build a React component for TreeMap similar to https://demos.telerik.com/aspnet-ajax/treemap/overview/defaultcs.aspx
Can you give us support on how we can get the information about the selections, and keep it updated at all times? Thank you,
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.