Completed
Last Updated: 26 Jun 2019 14:00 by ADMIN
I updated to the latest version of the kendo react components (3.2.1) and notices that if there are no records in the grid - the message is displayed in the first column rather than spanning - this behaviour is also happening in the demo - see the attached.
Completed
Last Updated: 18 Oct 2019 11:32 by ADMIN

Column locked with KendoReact Grid is not locked in the iPhone safari.  It's OK in Chrome phone simulator, but not in mobile. 

 

<Grid
                    style={{ height: '400px', width: '500px' }}
                    data={products}
                    reorderable
                >
                    <Column field="ProductID" title="ID" width="45px" locked />
                    <Column field="ProductName" title="Name" width="250px" />
                    <Column field="Category.CategoryName" title="CategoryName" />
                    <Column field="UnitPrice" title="Price" width="90px" />
                    <Column field="UnitsInStock" title="In stock" width="90px" />
                    <Column field="UnitsOnOrder" title="On order" width="90px" />
                    <Column field="Discontinued" width="120px" locked={true} />
                    <Column field="QuantityPerUnit" title="Additional details" width="250px" />
                </Grid>
Completed
Last Updated: 17 May 2019 11:53 by ADMIN
Release 2.11.0

Dropdownbutton doesn't work in FF 66.0.2 on maxOS

1. Click on the dropdownbutton
2. Clicking outside of the dropdownbutton menu
3. The dropdownbutton does not close

Under Review
Last Updated: 06 Apr 2020 09:12 by ADMIN

Steps:

1. Create web component with shadow-root.

2. Attach all.css styles behide shadow root.

3. Add compoent with icon from WebComponentIcon font.

Result:

Icon are not displayed properly.


Unplanned
Last Updated: 14 Jun 2019 05:14 by ADMIN
Created by: iConect Developer - Mike
Comments: 0
Type: Bug Report
1

Grid Header shifting when filtering column.

When a column is half visible, and it is filtered, a misalignment will occur between the header and the Grid content.

Video: https://www.screencast.com/t/PhOonptY2

Completed
Last Updated: 13 Sep 2019 07:23 by ADMIN
Release 3.3.0
Pressing enter in the ComboBox will select the first item with the same text value.

If we have items with the same text value and we navigate through them with the arrow keys and then select one with enter, the ComboBox will return the first item with that text instead of the currently selected one.
Completed
Last Updated: 12 Jun 2019 06:33 by ADMIN

When setting filter type in column to `boolean` it breaks when opening the column menu with the following JS error inside `filterCommon.js`:

TypeError: Cannot read property '0' of undefined

Here's a sandbox to see. Click the column menu next to each column header. Notice `Discontinued` column will cause a JS error: 

https://stackblitz.com/run/?file=app%2Fmain.jsx

 

The sandbox was taken from https://www.telerik.com/kendo-react-ui/components/grid/columns/column-menu/

 

We're using v3.1.0 but the sandbox has 3.2.0. Both versions have this bug. It seems 2.11.0 is the last working version.

Unplanned
Last Updated: 24 Apr 2020 04:55 by ADMIN
AutoComplete focused item is not set correctly if the items are with different height.

Currently, it is required to have the same height for the items, but this can be very hard in cases when the items are dynamic with various height.
Unplanned
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

Completed
Last Updated: 20 Oct 2020 10:28 by ADMIN
Created by: Kyle
Comments: 3
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.

Declined
Last Updated: 21 Jul 2020 10:24 by ADMIN
Created by: FIIG Securities
Comments: 3
Type: Bug Report
1

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".

Completed
Last Updated: 26 Jun 2019 14:19 by ADMIN
Created by: Daniel
Comments: 0
Type: Bug Report
0

The Switch layout is misaligned on IE 11.

54738802-5a28bf00-4bbe-11e9-91aa-7eb104343935.png (195×151)

This is reproducible in our demos as well.

GitHub issue: https://github.com/telerik/kendo-react/issues/220

Under Review
Last Updated: 02 Apr 2020 10:26 by ADMIN
Created by: Vlado
Comments: 11
Type: Bug Report
0

UPDATE: This is live code I prepared for you: https://stackblitz.com/edit/react-ts-dhhsaz?file=index.tsx

I get error:

 Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app

But error appears to be inside KendoDrawer component. I can't figure out what is wrong. This is my component:

import React, { useState } from 'react';
import { withRouter, useLocation, useHistory } from 'react-router-dom';

import { Drawer, DrawerContent } from '@progress/kendo-react-layout';
import { Button } from '@progress/kendo-react-buttons';



export const SidebarDrawer = (props:any) => {

    const items = [
        { text: 'Povezivanje', icon: 'k-i-inbox', selected: true, route: '/povezivanje' },
        { separator: true },
        { text: 'Notifications', icon: 'k-i-bell', route: '/notifications' },
        { text: 'Calendar', icon: 'k-i-calendar', route: '/calendar' },
        { separator: true },
        { text: 'Attachments', icon: 'k-i-hyperlink-email', route: '/attachments' },
        { text: 'Favourites', icon: 'k-i-star-outline', route: '/favourites' }
    ];

    const [expanded, setExpanded] = React.useState(true);
    const [position, setPosition] = React.useState(true);
    const [selectedId, setSelectedId] = React.useState(items.findIndex(x => x.selected === true));

    let positionMode = position ? 'start' : 'end';

    const handleSelect = (ev:any) => {
        setSelectedId(ev.itemIndex);
        setExpanded(false);
    };

    const handleClick = () => { setExpanded(prevState => !prevState); };

    const handleChange = () => { setPosition(prevState => !prevState); };

    const drawerProps = {
        expanded: expanded,
        position: positionMode,
        mode: 'push',
        items: items.map(
            (item, index) => ({ ...item, selected: index === selectedId })),

        onSelect: handleSelect,
    }

    return (
        <Drawer {...drawerProps}>
            <DrawerContent>
                {props.children}
            </DrawerContent>
        </Drawer >
    );

};

export default withRouter(SidebarDrawer);

And this is how I use it inside App component:

import React, { useState } from 'react';
import { hot } from 'react-hot-loader';
import { Button } from '@progress/kendo-react-buttons'
import { Grid, GridColumn, GridDetailRow, GridToolbar } from '@progress/kendo-react-grid';
import '@progress/kendo-theme-bootstrap/dist/all.css';

import 'bootstrap/dist/css/bootstrap.min.css';
import { Drawer, DrawerContent } from '@progress/kendo-react-layout';
import { BrowserRouter as Router, Route, Switch } from 'react-router-dom';

import urlConstants from 'ClientApp/constants/urlConstants'
import { Connecting } from '../containers/connecting/Connecting';
import SidebarDrawer from 'ClientApp/components/SidebarDrawer/SidebarDrawer';

export const App: React.FC = () => {


    return (
        <React.Fragment>
            <Router>
                <SidebarDrawer>
                    <Switch>
                        <Route exact={true} path="/" component={Connecting} />

                    </Switch>
                </SidebarDrawer>
            </Router>
        </React.Fragment>
            )
}

export default hot(module)(App);
Completed
Last Updated: 17 May 2019 11:49 by ADMIN
Release 2.11.0
Completed
Last Updated: 20 Oct 2020 10:32 by ADMIN
Created by: Adam
Comments: 1
Type: Bug Report
0

Hello Kendo React Team,

 

Here are a few bugs to address on the Kendo React Scheduler (3.6.0)...

 

Issue 1: November 3, 2019 Repeated on Week/Month Views

Visit https://www.telerik.com/kendo-react-ui/components/scheduler/views/month/ or https://www.telerik.com/kendo-react-ui/components/scheduler/views/week/, navigate to the first full week in November 2019. You will notice that 11/3 is repeated for Sunday/Monday. I'm wondering if this issue is related to daylight savings time. The calendar does not have a timezone configured (just uses the default UTC and my local timezone is PST).

 

Issue 2: Clicking an empty all day slot does nothing.

The onSlotClick callback should be fired when clicking on an all day event. I currently have to add an event listener using document.querySelectorAll("[data-slot-allday='true']"); to get the right behavior (definitely not ideal).

 

Issue 3: onItemDoubleClick and onSlotDoubleClick do not work on mobile devices.

My current solution to get everything to work on desktop and mobile is to use the onItemClick and onSlotClick and to not integrate useCallback with double clicking.

 

Suggested Improvements:

  • The documentation is silent about onItemClick, onSlotClick, onItemDrop, etc. These are essential to extend the behavior of the scheduler. I had to dig through the node modules directory and look through the .ts files to figure out how to use these work.
  • The mobile experience is awful. I miss the isMobile prop on the kendo-scheduler-react-wrapper. Whether you reintroduce that prop or add better css for smaller viewports, it would be greatly appreciated.

 

 

Declined
Last Updated: 26 Jun 2019 14:05 by ADMIN
Created by: Nathaniel
Comments: 1
Type: Bug Report
0

I am using the ComboBox component in IE11.  When the control has a value, the clear button covers the select arrow at the right of the control.  This occurs because IE11 does not allow nested calc() calls in the CSS width property, e.g. 

.k-dropdown-wrap .k-clear-value {
    right: calc(calc( 0.75rem + 17px) + 6.5px);
}

Removing the inner calc() works well enough:

.k-dropdown-wrap .k-clear-value {
    right: calc(( 0.75rem + 17px) + 6.5px);
}

Unfortunately, this rule seems to originate from a CSS function call to which I do not have access.  Is it possible to remove the inner calc()?

Completed
Last Updated: 20 Oct 2020 10:25 by ADMIN

When using the <Window> component, there is an issue trying to maximize, when a parent element has positioning (ie:  position: absolute, position: relative).  The calculation for defining the width uses window.innerWidth (similar for height).  However, for placement, it uses top and left = 0.  

You can see a sample of this on StackBlitz:

https://stackblitz.com/edit/react-59kqss

This is a straight copy of https://www.telerik.com/kendo-react-ui/components/dialogs/window/controlled-mode/, but added the additional styles to the parent <div>.

Version is 3.14.

 

Thanks.

Completed
Last Updated: 26 Jun 2019 14:23 by ADMIN
Created by: Nathaniel
Comments: 1
Type: Bug Report
0

When using the DialogActionBar, its flex CSS property is flex:1 0 0.  For some reason, this is not a valid value in IE11, and I need to specify the flex values explicitly:

.k-dialog-button-layout-stretched .k-button {
    flex-grow: 1;
    flex-shrink: 0;
    flex-basis: 0px;
}

Can this be added to the original stylesheet so it works out of the box?

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 }
    ] }
];
Completed
Last Updated: 17 May 2019 11:55 by ADMIN
Release 2.10.0
TimePicker is missing the localization properties.
1 2