I discovered a lack of parity between the React and Angular implementations of the TabStrip/TabStripTab components. Specifically, in the React version the "title" prop determines the contents inside the resulting <k-link> CSS class, whereas the Angular version allows you to set a template, for more complex tab header components.

This became an issue for me, because we have overridden the CSS for a custom progress tracker component built on the tab strip in an Angular implementation. I am now tasked with replicating the component in React, but had to resort to my own TabStrip/TabStripTab classes, instead of being able to use your components. (My goal is to be able to use the existing CSS, maintained by our UX team, out of the box.)

Hope that made sense. Feel free to contact me if it's not clear what I'm asking for, or if there is already a solution to this. Thanks!

React version:

Angular Version:

To Whom It May Concern,

I am requesting the Kendo team to implement a new feature of programmatically setting a Grid's page for the Kendo React Grid. 

This can be accomplished by having a listener for the Grid's state. For example, when the Grid's skip props is changed, the Grid's page will also change to the number of elements skipped.

Please consider implementing this feature.

Thank you.

Sincerely,

Andrew J. Yang

Keysight Technologies

in React Dialog, the Dialog or the overlay, need to be focused for the Escape Key to work and close the dialog, whereas in the jQuery Dialog, it works globally without a specific focus...

Not only would I like control over the group order (like from this thread https://feedback.telerik.com/kendo-react-ui/1523636-need-to-be-able-to-have-more-control-over-the-order-of-groups-in-the-kendo-grid-sort-on-the-text-is-insufficient), it would be awesome if we could sort groups themselves.

I understand that the current set up sorts children within groups but not the groups themselves. However, sorting within and between groups is a bit more intuitive to the user when they see visually-grouped information and try to sort on it => most of our users expect the groups to get sorted as well.

Although I can write my own sorting functionality, it can get out of hand quickly with ascending/descending, numeric vs alphabetic columns, and multi-sort vs single sort, but KendoReact already has the capability to sort in these three ways with its non-grouped grid functionality.

In order to display  KendoReact Chart on mobile phones on a horizontal screen, CSS "rotate(90deg) translate(...)"   is applied to KendoReact Chart,

but the coordinates of tooltip are incorrect.

     let w = window.innerWidth || document.documentElement.clientWidth || document.body.clientWidth;
     let h = window.innerHeight || document.documentElement.clientHeight || document.body.clientHeight; 

     let x = (h-w)/2;
     let ts = "rotate(90deg) translate("+x+"px,"+x+"px)";
     const maxstyle={
        transform:ts,
        width:h,
        height:w,
        top:0,
        left:0,
        paddingLeft:5,
        paddingRight:5,
        paddingTop:5,
        transformOrigin:"center center",
        background:'#f5f5f9',
        overflow:"hidden",
        position:"fixed",
        zIndex:10000
    };

When then CSS "rotate(90deg) translate(...)" is applied to KendoReact Chart, the coordinates of tooltip are incorrect.
In order to display  KendoReact Chart on mobile phones on a horizontal screen, CSS "rotate(90deg) translate(...)"   is applied to KendoReact Chart,

but the coordinates of tooltip are incorrect.

sourcecode:

I don't know how to implement rowspan

Like in the jQuery counterpart, when I click on a cell to edit the value - I should be able to tab over to the next cell to edit it.

Hi, when entering https://www.telerik.com/kendo-react-ui/getting-started form npmjs.com, I end up on a page with "Try Kendo UI for React" heading, but whole header comes from Kendo UI for Angular project

I would like to use my custom component as the chat input. Is it possible to add new prop to chat component? Similar to DatePicker's "dateInput" prop.

Hi,

the current filter is great but a little bit difficult to use. I would like to see an inline filter like the following screenshot:

It is used by many applications. Just to name a few

* Gitlab (where the screenshot is from)
* Contentful (CMS)
* Google Cloud Console

Hi there,

I can see there is a column chooser component for the Angular Data Grid e.g. https://www.telerik.com/kendo-angular-ui/components/grid/columns/menu/#toc-column-chooser-item but there is not an equivalent for the React Data Grid (unless you code it yourself).

The DevExpress React Grid does have this feature https://devexpress.github.io/devextreme-reactive/react/grid/docs/guides/column-visibility/ so we were wondering if such a thing is planned React Data Grid?

Thanks very much,

James

We would like to use Kendo React to build a micro frontend UI but we did not found any relevant information that this is currently supported.

The main issue we are facing is how it isolate Kendo theme styling between different micro frontends.

Let's say we have 2 micro frontends A and B:

- A is using Kendo v6.

- B is using Kendo v7 (or some other future/past version).

Both of them will include their global Kendo styles which will collide.

After some investigation, we came up with 2 possible approaches:

1. Isolating micro frontends using shadow DOM. This is the most common technique but unfortunately not supported by Kendo React yet.
2. Prepend custom class to all Kendo CSS selectors (for example ".microfronend-a .k-button" instead of just ".k-button").

We have experimented with the second approach and it seems like a way to go. It also required to append all popups to root DOM node of a micro frontend which can be done easily using PopupPropsContext.

But adding a class to all Kendo CSS selector is technically not a trivial task. It would be nice if Kendo supported this out of the box, for example by providing some SCSS configuration variable.

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;