Approved
Last Updated: 16 Jan 2020 16:51 by ADMIN
Created by: Ajay
Comments: 1
Type: Feature Request
5
When the available space for the Menu go under specific width the Menu should be hidden and a hamburger style button should be shown to access the Menu. This feature has to be added to our Menu component to make it responsive.
Completed
Last Updated: 16 Jan 2020 16:48 by ADMIN
Created by: Justin
Comments: 3
Type: Feature Request
7

It would be great to have a TreeList component similar in appearance and behavior to the jQuery TreeList (https://demos.telerik.com/kendo-ui/treelist/index), but with the kind of support for virtual scrolling built into the native KendoReact Grid component.

A React wrapper exists for the jQuery TreeList, but it still doesn't play nicely with React, and in any case only supports paging for displaying large data sets, which is inherently not intuitive for displaying tree structures where parent / child hierarchies might span multiple pages.

My sense is this native component would basically be the Grid, but with support for hierarchical data, including drag-and-drop re-ordering of parent / child relationships.

Thanks for considering this feature.

Under Review
Last Updated: 10 Jan 2020 13:17 by ADMIN

Hi,

  we have a feature request as per description, value isn't changed when manually entering numbers in the field, it only changes when selecting a presented date. When manually entering date, value remains null so reset is actually changing null to null, not the entered value to null. Your colleague mentioned that the feature of exposing mask to be controlled would make it possible to clear the mask.
Please refer to this github issue for more detailed information, containing stackblitz example and gifs of an user case, as it was an ongoing discussion.
Please implement an option to properly reset partially entered dates.

https://github.com/telerik/kendo-react/issues/368

Approved
Last Updated: 09 Jan 2020 14:37 by Ofer
Add floating labels on the DatePicker and DateTimePicker.
Completed
Last Updated: 09 Jan 2020 08:38 by ADMIN
Release 3.10.0

Hello, 

I would like to request for the filter component to be supported in the KendoReact suite as it is in the ASP.NET Core UI suite.

One aspect is the hierarchical structure which can support complex filter scenarios but also the support to persist state of a set of filters.

Thank you

Declined
Last Updated: 24 Dec 2019 08:07 by ADMIN

In the case of multiple columns headers, the column width of the KendoReact  TreeList  is invalid

 

 

const columns = [
  
   { field: 'name', title: 'Name', width: 300, expandable: true }
    ,
    { title: 'Employee Details', width: 600, children: [
        { field: 'position', title: 'Position', width: 500 },
        { field: 'fullTime', title: 'Full Time', width: 100 }
    ] }
];
Declined
Last Updated: 24 Dec 2019 08:03 by ADMIN
When can I release the Spreadsheet in Kendo UI for React,not Wrapper
Approved
Last Updated: 18 Dec 2019 11:32 by ADMIN
Created by: J
Comments: 5
Type: Feature Request
3
Is there any prop so that I can trigger another event on press of cancel button on KendoCalender.
Approved
Last Updated: 18 Dec 2019 07:24 by ADMIN
Created by: iConect Developer - Mike
Comments: 1
Type: Feature Request
0

This support ticket is a feature request for a React version of the DropDownTree component: https://demos.telerik.com/kendo-ui/dropdowntree/index

For now I've hacked together something using a span styled like the collapsed DropDownTree, a React Popup and a React TreeView.  It would be great if this control could be adapted for React and added to the dropdowns package.  Unless there is an easy way to accomplish this using the React Dropdown and the React Treeview?

Approved
Last Updated: 18 Dec 2019 06:58 by ADMIN
Created by: iConect Developer - Mike
Comments: 0
Type: Feature Request
0

Add render prop for the SplitButton.

This will allow changing the main button and also the button that opens the DropDownList.

Approved
Last Updated: 18 Dec 2019 04:38 by Kirill
Created by: Kirill
Comments: 2
Type: Feature Request
1

Existing implementation of Scheduler component has a very limited customization support. To cover some real use-cases we need:

  1. Conditionally hide Scheduler Header and Footer. This is possible with CSS, but still makes sense to have props for that.
  2. Customize tooltip content when hovering on the event. Currently tooltip is a one line text, but adding support of a larger popups on hover would allow to show additional info associated with that event. Please consider adding a prop to pass custom component for tooltip/popup rendering (similar to how Custom cells work in Kendo Grid)
  3. Customize event component. Is there a way to have multiline text in the event component? Currently it is way to limited to show custom content e.g. adding custom icons is impossible.
  4. All events in the same group have a same color when displaying. Please consider adding individual color support for each event. This would help to support error states for events.
  5. Custom onDelete/onDoubleClick handlers. We would like to have custom implementation of Delete confirmation and Edit form.

Please advise on how to overcome those limitations as a short term solution and consider adding more Scheduler customization abilities to your Roadmap.

Example of highly configurable Scheduler/Timeline component:  https://js.devexpress.com/Demos/WidgetsGallery/Demo/Scheduler/Timelines/React/Light/

Pending Review
Last Updated: 12 Dec 2019 08:01 by ADMIN
Created by: Vitaliy
Comments: 5
Type: Feature Request
2

Hello,

I have two Menus and I need to customize their popups differently. Can I specify somehow Menu Popup id or className?

As I can see Popup component has className property, but it is hard-coded in MenuItemInternal.prototype.getPopupClassName and neither Menu nor MenuItem classes are used in popup.

Any suggestions?

Thanks.

 

Under Review
Last Updated: 11 Dec 2019 07:16 by ADMIN
Please add an Encoded Prop to the GridColumn for KendoReact that works like the "encoded" property on columns in the jQuery version to allow us to pass unencoded Html to the cells of our KendoReact Grids. Thanks so much for any assistance in this matter!
Declined
Last Updated: 06 Dec 2019 08:05 by ADMIN
Created by: FIIG Securities
Comments: 1
Type: Bug Report
0

There seems to be bug in the React Grid around date formatting inconsistencies:


Current behavior
When entering a date format of {0:dd/MM/yyyy} for a ColumnData prop, when in edit mode a calendar picker shows the date format as US date of MM/dd/yyyy.Expected behavior
The date should show as dd/MM/yyyy per the requested date format.Minimal reproduction of the problem with instructions
Create a Kendo grid with one column with following ColumnData:
const settlementDate: ColumnData = {
field: 'settlementDate',
title: 'Setlement Date',
format: '{0:dd/MM/yyyy}',
filterable: true,
filter: 'date',
editor: 'date'
};
Note that the date is displayed as MM/dd/yyyy
Change the format to "dd/MM/yyyy"
Note that when in view mode the date is displayed as "dd/MM/yyyy".
What is the motivation or use case for changing the behavior?
Currently I have to create a custom date cell for every instance of using a date field in my grid which is less than ideal.Environment
Package versions:
@progress/kendo-data-query@1.5.2
@progress/kendo-dateinputs-react-wrapper@2019.4.1014
@progress/kendo-base-component-react-wrapper@2019.2.606
@progress/kendo-drawing@1.6.0
@progress/kendo-dropdowns-react-wrapper@2019.4.1014
@progress/kendo-base-component-react-wrapper@2019.2.606 deduped
@progress/kendo-react-data-tools@3.9.0
@progress/kendo-react-common@3.9.0
@progress/kendo-react-dateinputs@3.9.0
@progress/kendo-date-math@1.2.0
@progress/kendo-react-buttons@3.9.0
@progress/kendo-react-common@3.9.0
@progress/kendo-react-popup@3.9.0
@progress/kendo-react-dropdowns@3.9.0
@progress/kendo-react-common@3.9.0
@progress/kendo-react-popup@3.9.0
@progress/kendo-react-grid@3.9.0
@progress/kendo-react-common@3.9.0
@progress/kendo-react-inputs@3.9.0
@progress/kendo-react-common@3.9.0
@progress/kendo-react-popup@3.9.0
@progress/kendo-react-intl@3.9.0
@telerik/kendo-intl@1.5.2
@progress/kendo-react-pdf@3.9.0
@progress/kendo-file-saver@1.0.7
@progress/kendo-theme-default@4.7.0
@progress/kendo-theme-material@3.5.0
@progress/kendo-ui@2019.3.1113Browser:Chrome (desktop) version 78.0.3904.108
System:
Platform: Windows

Other information:
It appears that there is an incompatibility as to what a text display field requires as opposed to what a date picker requires. For text display it requires a format of '{0:dd/MM/yyyy}' whereas the datepicker requires a format of "dd/MM/yyyy".

Pending Review
Last Updated: 26 Nov 2019 18:18 by ADMIN
Created by: Kyle
Comments: 2
Type: Bug Report
1

In the KendoReact Scheduler component, there is a bug when you try and change the date for an event.

Steps to reproduce:

  1. use an editable scheduler component in your website
  2. click on an event in the scheduler to open the modal
  3. in the modal click on the date selector (calendar) icon next to Start or End.
  4. The date selector is behind the modal

Looks like you need to change the z-index of the date selector if it is a child of a modal.

 

Thanks! I attached screen shots.

Approved
Last Updated: 22 Nov 2019 07:11 by ADMIN
Created by: Hugo
Comments: 2
Type: Feature Request
1
Hello,

I would like to know if there are any Kendo React components to suit Bottom navigation functionality as per Material Design

Thanks in advance,
Approved
Last Updated: 21 Nov 2019 10:35 by ADMIN

Hi Guys,

In GridProps for KendoReact Grid there is an error in the type information:

Found here: https://www.telerik.com/kendo-react-ui/components/grid/api/GridProps/#toc-rowrender

In the GridProps.d.ts file it is:

    /**
     * Fires when a row is about to be rendered. Overrides the default appearance of the row.
     */
    rowRender?: (row: React.ReactElement<HTMLTableRowElement>, props: GridRowProps) => React.ReactNode;

This should be changed to:

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

 

Note that the React.ReactElement definition is:

    interface ReactElement<P = any, T extends string | JSXElementConstructor<any> = string | JSXElementConstructor<any>> {
        type: T;
        props: P;
        key: Key | null;
    }

 

So the first type parameter should be the props typ.

I noted this while making use of it. After changing it it behaves sensibly. Worked around in my case by using 'as any' to void the type clash.

Cheers,

Stuart

Declined
Last Updated: 21 Nov 2019 06:08 by ADMIN
Created by: Ruslan
Comments: 2
Type: Feature Request
0

 

Q:

From the last conversation through the webinar

jQuery Filter looks cool! What about Kendo React Filter?

A:

Right now we do not have a KendoReact Filter component, but feel free to drop us a line in our feedback portal and we will consider implementing it.


Under Review
Last Updated: 20 Nov 2019 13:41 by ADMIN

Hello,

I have a request that for some tables the user needs arrows to be able to scroll left and right horizontally through the grid content. Is there a functionality like this provided out of the box by Kendo Grid, can you please point me to the docs or provide an example? I have provided an image to reflect this.

Thank you,

Andrei

Pending Review
Last Updated: 19 Nov 2019 08:50 by ADMIN

Hello

There was an error calling “ chart.surface.redraw() ” 

 

  onRender = (args,mapValues,stackedOrderBy) => {              
        const chart = args.target.chartInstance;      

        const valueAxis = chart.findAxisByName("valueAxis");
        const categoryAxis = chart.findAxisByName("categoryAxis");

        if (!chart) return;        

           let x= 1;
            if( stackedOrderBy!="Ascending")
                x=-1;

            let axis = categoryAxis.options;

            axis.categories = axis.categories.sort(function (a, b) {
                if (mapValues[a] < mapValues[b]) {
                return -1*x;
                }
                if (mapValues[a] > mapValues[b]) {
                return 1*x;
                }

                return 0;
            });


            chart.surface.redraw();

                           
1 2 3 4 5 6