Completed
Last Updated: 23 Oct 2020 09:37 by ADMIN
"@progress/kendo-react-grid""^3.15.0"
  1. Configure a Kendo React Grid with paging on a react-bootstrap tab that is hidden on initial load
  2. Navigate to the tab - the Grid is rendered with truncated paging controls and no item count
  3. Resize the screen in any way - the full paging controls and item count are restored

Is there a workaround for this issue?

Completed
Last Updated: 20 Oct 2020 10:40 by ADMIN
The scheduler component does not work in Internet Explorer. We need to support IE 11 for our costumers. On the Kendo React example page I get an error that the  'object does not support property or method 'entries'.  In the code we're developing the error is similar, but refers to 'forEach' instead of entries. 
Completed
Last Updated: 20 Oct 2020 10:35 by ADMIN
Created by: Michael
Comments: 1
Type: Bug Report
0

On your Grid Demos:   When ever you try to edit a text cell the cursor always goes to the end of the text box

 

For example, go to your demo:

 

https://www.telerik.com/kendo-react-ui/components/grid/editing/editing-inline/

 

- Edit the first row.  Try to type something before "Chai" - the cursor will jump to the end of the textbox

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.

 

 

Under Review
Last Updated: 20 Oct 2020 10:30 by ADMIN

Problem:

The DateTimePicker does not work in IE11 due to it's failure to fully support the shorthand syntax for flex (https://github.com/philipwalton/flexbugs#flexbug-4). In order for it to work in IE11 flex-basis needs a unit defined and therefore does not support calc() in this scenario.

Potential Fix:

If you break out flex-grow, flex-shrink and flex-basis then calc() can be used for flex-basis.

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.

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: 20 Oct 2020 10:20 by ADMIN

Hi,

I'm seeing a bug in TreeList which seems to be related to how locked column positions are being set.  The issue I'm seeing is when I scroll to the right the columns either overlap of have a gap between them.  See image below.

I also created a demo that demonstrates this issue: https://stackblitz.com/edit/react-lwp4ua?file=app%2Fmain.jsx


Seeing this issue in:

"@progress/kendo-react-treelist""3.12.0",
Planned
Last Updated: 01 Oct 2020 11:55 by ADMIN

Hello,

 

After taking a look at your example in the documentation here (which doesn't seem to be working) https://www.telerik.com/kendo-react-ui/components/charts/chart/elements/selection/#using-selection-as-navigator 

I fixed the onSelectEnd function and got it working. However, the selection chart is reloading the data every time onSelectEnd changes this.state.min and this.state.max.

Here is the example:

https://stackblitz.com/edit/react-nub1sc?file=app/main.jsx 

As you can see, this makes for a clunky UI.

 

If this isn't a bug, do you have suggestions on how to fix this?

Thanks,

Orla

Unplanned
Last Updated: 28 Sep 2020 07:06 by ADMIN

Hi,

I have Scheduler vertical timeline with an user group and more users I add the wider is every slot.  Example 2 users https://stackblitz.com/edit/react-dttghr?file=app%2Fmain.jsx . Example 4 users https://stackblitz.com/edit/react-dttghr-a3nor3 the slot is double in width in comparation with 2 users. Can I control this somehow?

Unplanned
Last Updated: 27 Jul 2020 07:21 by ADMIN

With the ArcGauge component, when you set the rangeLineCap to something other than 'butt' (ie:  round or square), the indicator does not line up with the tick lines.  This leads to misleading values.  Please look at this StackBlitz:

 

https://stackblitz.com/edit/react-itztql

 

This will show the comparison between round and butt rangeLineCaps. 

From the screenshot as well, the ArcGauge on the right looks like the value is greater than 0, resulting in the user being mislead on the result.

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

Declined
Last Updated: 03 Jul 2020 06:00 by ADMIN

I am trying to lock first column in Grid, when I used the instructions in Kendo React documentation I tried the same but as you see in screenshots it's not working.

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


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);
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 }
    ] }
];
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

Pending Review
Last Updated: 28 Oct 2019 10:33 by ADMIN
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>
1 2