Please allow the Switch component to accept a title prop so that the Tooltip component can be used with Switch. Switch doesn't really support long labels, or labels at all in some themes, so it would be nice to be able to use Tooltip component with Switch component.

Currently the TileLayout will allow you to drag a Tile when you click and drag anywhere within the Tile. This doesn't combine very well with content within a Tile that might have click-and-drag functionality or even just click functionality. A small click within a Tile causes the Tile to visually "lift up" in preparation for dragging.

It'd be nice if there were a setting to enable dragging only on the Tile header portion or somewhere.

Currently I have to add a toggle somewhere on the page that disabled or enables dragging.

Hello,

I am using tooltip component for a long desciption field in my grid cell. And I am using it as it will encapsulate Grid component (like the example below) as it is suggested in this page.

<Tooltip openDelay={100} position="right" anchorElement="element"> <Grid>... </Grid> </Tooltip>

My grid has a date field and I am using columnMenu for filtering (GridColumnMenuFilter). An error occurs when I hover the text of date field and says : 

Tooltip(...): Nothing was returned from render. This usually means a return statement is missing. Or, to render nothing, return null.

I also trid to replicate the problem in the example on this page and it gives the same error. I forked the project and you can check it from https://react-ed5jns.stackblitz.io/

Simply move the cursor over month/day/year in a date filter area and see the problem. This seems like a bug. Or if there is any solution to this, I would like to see a workaround.

Thanks

Hi,

I've got a large form I'm making. When the page the form is on first renders, I maker a server call and get back a large javascript object:

serverData = {id: "1", ClientID: "1423", EstSentDate: "2021-07-08", .... }. The date strings are ODCB standards for date strings.

The form displays the current values of all these fields. For all the other field types, I give the form the prop initialValues={serverData}, and if the field names match the object keys, it populates the field with the data nicely.

The datePicker is encountering an error though. It looks like it expects a Date object and not just a string. Is there something I can do within the DatePicker component, or the field containing it, to resolve this, without having to parse the entire data set I receive for all dates and convert them to Date objects, and feed that into a new object to pass to the form?

Being able to populate the entire form with the simple line initialValues={serverData} would be the best outcome for us.

Hi Team,

we are looking same property in Kendo Tree View React Version.

https://docs.telerik.com/kendo-ui/api/javascript/ui/treeview/configuration/dataspritecssclassfield

could you pls check the feasibility and add the same?

The ListView component has an item prop that allows you to specify the render component. That component receives ListViewItemProps. The ListViewItemProps type is not exported and cannot be properly imported elsewhere.

Hi Team,

I'm facing below issue when manually enter the value in the datepicker.

Control : DatePicker

 <DatePicker defaultValue={value} format="dd/MM/yyyy"  />

Step 1: Manually I'm trying to enter the data as 01/01/2021 and clicked outside the datepicker control ( now the focus is out of the datepicker ).

Step 2: Now try to change the date (day) by entering  "2".  (Our Expectation is system should display the date as 02/01/2021 instead it is appending the date and displaying as 12/01/2021)

Every time system is expecting the user to clear the existing value and then enter the new value. 

Can you take this as feature request. Value should not get append to existing value. It should overwrite.

Reference Ticket URL : https://www.telerik.com/forums/datepicker-when-user-enter-the-date-manually-the-value-getting-appended-with-the-previous-value

If this is taken as feature request when will it get delivered.

We have two issues with grid with virtual scroll.

Both are registered on github.

First one is really blocking us: https://github.com/telerik/kendo-react/issues/1010

Second one we found on Safari, it's also very critical for our customers: https://github.com/telerik/kendo-react/issues/1013

Version: 4.7.0. Please note that version specified in Additional information does not make sense as we use Kendo React not Kendo UI.

Can you help us somehow?

Click icon to close as well as open

Hi Team, 

I have found an issue in the Grid Component that I think needs some attention, see below.,

## Current behavior
My GridColumns are not styling correctly when i hide/show them based on an edit state (for example). Some that have no width restrictions will the shortened then not lengthed.

## Current Version

KendoReact 4.8.0

## Expected behavior
If I hide/show a GridColumn, its width should not affect other GridColumns, only the Grid overall.

## Minimal reproduction of the problem with instructions
Example: https://stackblitz.com/edit/react-ngpvuj?file=app%2Fmain.jsx

Instructions:
1. View how age is the only column visible with a width attr
2. Click "Switch Mode" and notice how 'Id' is not added, but a width of 80 is now applied to the 'lastname' column, the same width as age
3. Click "Switch Mode" back to view, and see how id is removed and a width of 60 is applied to the 'firstname' column.

## Investigation:
Some investigation in the DOPM revealed that the issue is centred around the <colgroup> of the Grid's <table>:
- step 2 does the following to the <col>s in the <colgroup>
  - add a new col to the beginning with a width, for the Id column
  - add a new col to the end with a width, for the Age column
  - DOES NOT clear the width of the col group that used to be the age column

- step 3
 - Simply removes the last <col> in the group. Does not affect hte attributes of the remaining <col>s

I hope this was informative and can be resolved soon.

Kind Regards,
Grant

When a user focus an empty DatePicker input using tab, the caret starts at the end (right side) of the input.

We need it to start at the left side, so the user can type without having to go all the way back to the left.

toODataString throw exception on text filter changed from is null to contains. 

https://stackblitz.com/edit/react-ertg4z?file=app%2Fmain.jsx 

Repro step:

1. Choose filter by Name which is using text filter.

2. Change filter from Is null to contains.

3. toODataString threw exception.

Repro:

1. Create a DateTimePicker.
2. Use its value prop to programmatically control the value the control uses.
3. Add clickable Button (or other means) to programmatically set the value to an invalid date (i.e. something like new Date("invalid!").
4. Click the Button.  The date displayed becomes "NaN/NaN/NaN 12:NaN PM".  I suppose this is reasonable.
5. Now, click the calendar popup icon on the right-hand side of the component.

Expected:

Displays a calendar popup, perhaps defaulting to the current date & time.

Actual:

Throws an exception visible in the JavaScript console.  Replaces the UI with an error message.

Proof-of-Concept:

https://stackblitz.com/edit/react-gvipiu?file=app%2Fmain.tsx

import * as React from 'react';
import * as ReactDOM from 'react-dom';

import {
  DateTimePicker,
  DateTimePickerChangeEvent,
} from '@progress/kendo-react-dateinputs';
import { Button } from '@progress/kendo-react-buttons';

const App = () => {
  const [date, setDate] = React.useState(new Date());

  const handleChange = (event: DateTimePickerChangeEvent) => {
    setDate(event.value);
  };

  const handleClick = () => {
    setDate(new Date('invaild!'));
  };

  return (
    <React.Fragment>
      <div className="example-wrapper">
        <p>
          (use Alt+<code>↓</code> to open the date-time selector, <code>←</code>{' '}
          and <code>→</code> to navigate, <code>↑</code> to increment and{' '}
          <code>↓</code> to decrement the value)
        </p>
        <DateTimePicker onChange={handleChange} value={date} />
      </div>
      <Button onClick={handleClick}>
        Click me, then the calendar, to break the DateTimePicker.
      </Button>
      <div>{date?.toString()}</div>
    </React.Fragment>
  );
};

ReactDOM.render(<App />, document.querySelector('my-app'));

Hi Team,

I would like to report the following Major bug for KendoReact v4.9.0:

Duplicate:
1) Open the Datepicker Demo page
2) Open any of the datepickers and click the month name, as you will see a few months are hidden on the right had side.
  The same behaviour continues if you click the year or decade.

Thanks and kind regards,

Grant

PS. This feedback form only allows me to select a "KendoUI for jQuery" version number.

Looking at the deliver1.PNG, there is a grid with a 'MultiColumnComboBox' component inside one of the columns. When a name is removed from a role in one row (deliver2.PNG), then that row is deleted/removed, the row below it moves up but loses its name on the UI but the data is not effected (deliver3.PNG).

Can confirm all data is intact when passing information to the 'MultiColumnComboBox' component, it's just a UI bug which doesn't display the value that was selected in the unedited/deleted row. Can also confirm this bug exists in other grids with 'MultiColumnComboBox' components.

The code path is as follows in images code1.PNG, code2.PNG, and code3.PNG. It can be seen there is a UserComboBoxCell element which returns a component called 'EditableGridMultiColumnComboBoxCell'. It is this component that uses the the 'MultiColumnComboBox' component.

Hi team, 

Im not sure if this is a bug or an incomplete feature, so please advise.

1) TabStrip / Window behavior in v4.8.0 with bootstrap theme 4.40.0, see https://stackblitz.com/edit/react-wdzeyo?file=index.html
Please note the style and behaviour of the window, its above the modal and can be dragged anywhere on the screen, even though it was rendered from within the TabStripTab component

2) TabStrip / Window behavior in v4.9.0 with bootstrap theme 4.42.0, see https://stackblitz.com/edit/react-zhkfdp?file=app%2Fmain.jsx
As you can immediately see in this example, the TabStripTab heading is also above the modal, an obvious bug
My concerns are around how the window can no longer be dragged outside the TabStripTab container. Is this by design, beacuse in my use case, my tabs are smaller than my windows.

Note: I have not tested the windows with any other components.

Please advise.

Many Thanks,
Grant