Create a custom view with only specific dates shown in the Scheduler.

For example, the Sheculder will only show the dates 02/02/2020, 02/10/2020 and 02/20/2020.

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

Request:

- provide a boolean property "virtualScrolling" on component GridColumnMenuCheckboxFilter which allows rendering a large list of filter options without delay

Discussion:

- https://www.telerik.com/forums/gridcolumnmenucheckboxfilter-virtual-scrolling

Use case:

- there are a lot of options to filter already in memory

- the filter dropdown has to open quickly (it opens slowly now, because there are so many options)

- after opening, the user sees a huge list (i.e. a long scrollbar)

- so he starts making the list of options smaller using the search input

Here's a screenshot with 100 options. 

Alternatives:

From a developer point of view I think a scrollable filter is the most convenient way to handle the problem.

An alternative would be to provide a handler whenever the user selects a combobox in the GridColumnMenuCheckboxFilter. Then we could cut the number of options after a threshold and an option / combobox labelled "show more". When this is clicked, the filter options are re-rendered, the lists gets longer - and the user will get annoyed and will making the list of options smaller using the search input.

An other alternative would be to have a possiblity to force the user right away to use the search box. Instead of showing the list of checkboxes a text would be shown: "1258 options. Please refine your search input." But this would be a more invasive option.

Add parseFormats option to the KendoReact DateInputs (DateInput, DatePicker, DateTimePicker etc).

The option is expected to work as the parseFormats one available in Kendo UI:

https://docs.telerik.com/kendo-ui/api/javascript/ui/datepicker/configuration/parseformats

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.

It would be useful to add the `title` prop to the `Button` and `Chip` components. So that we get extra information in the default browser tooltip or use the `Tooltip` component for a customized look.

Add a shared note property for the Chart.

This property should allow rendering a note for multiple series items similar to the shared tooltip funtionality.

When the listbox has many items (roughly 200 and growing) the item attribute makes the listbox act slow when you want to click the item.
Even if the item render only returns the same value as not setting the item attribute. It seems like all the items re-render when it gets clicked?

Also in this example https://www.telerik.com/kendo-react-ui/components/listbox/customization/ it is possible to drag and drop a custom item.
But this is not working when we copy exactly the same code from the example. The drag event gets triggered but nothing happens. 
Both lists have items to avoid this bug: https://github.com/telerik/kendo-react/issues/1300

I can post my source code but it is literally the same as the example. When we remove the item attribute the drag and drop works again. 

Hi

I have been using Kendo React Scheduler and soon going to integrate it with our product. 

I came across a use-case/functionality requirement. Currently, with the Month View, when we have too many events in the view, we have the functionality of drilling down into the day view by clicking on three dots (I will refer to this as "View More" functionality). Very helpful indeed.

My use-case was when in the week view, we still have limited space per day in small dimensions for the calendar which can lead to the squashed arrangement of events on the time scale as well in the all-day section.

So I was thinking if we could have the same "View More" functionality in Week view as follows:

• Specifying the max number of events to be displayed for all-day view will render those events plus any additional like a "View More" functionality to drill down into Day view.
• Specifying the max number of events to be displayed for the same time frame will render those events plus any additional like a "View More" functionality to drill down into Day view.

Let me know if any other concerns or ideas around this may arise.

Thanks

Aman Gupta

As it happens, none of the existing ways of setting icons in the Button component work with either of the icon libraries we are using, which are:

1. Google Material Symbols, which uses ligatures to select icons rather than class names.
2. Material Design Icons via @mdi/react and @mdi/js, which renders programmatically generated inline SVGs.  These icons technically can be downloaded as finished SVGs for use with the imageUrl property, but only a single icon at a time, which is significantly less convenient than having access to the entire library at once when using the @mdi packages.

Rather than try to separately add specific support for these (and a thousand other) icon strategies, however, you could add support for both (and a thousand others) at once by just having something like an iconJsx property.  It would accept JSX.Element, and whatever it is given gets rendered inside the span.k-button-icon.k-icon.

So you could do something like this...

<h1>How will you attack?</h1>
{/* Google Material Symbols */}
<Button iconJsx={<span className="material-symbols-outlined">local_fire_department</span>}>Fire Breath</Button>
{/* @mdi/react + @mdi/js */}
<Button iconJsx={<Icon path={mdiKabaddi} />}>Target Weak Spot</Button>
{/* A poop emoji */}
<Button iconJsx={<span role="img" aria-label="poop">💩</span>}>Bio Weapon</Button>

To get something like this...

<h1>How will you attack?</h1>
<button class="k-button k-button-md k-button-rectangle k-button-solid k-button-solid-base k-rounded-md">
  <span role="presentation" class="k-button-icon k-icon">
    <span class="material-symbols-outlined">local_fire_department</span>
  </span>
  <span class="k-button-text">Fire Breath</span>
</button>
<button class="k-button k-button-md k-button-rectangle k-button-solid k-button-solid-base k-rounded-md">
  <span role="presentation" class="k-button-icon k-icon">
    <svg viewBox="0 0 24 24">
      <path d="M11.2 10.6C12.2 11.6 13.4 12.1 14.8 12.1L14.9 14.2C13 14.2 11.3 13.5 9.8 12.1L9.1 11.4L6.8 13.8L9 15.9V21.9H7V16.7L5.7 15.5V17.7L1.5 22L.1 20.6L3.7 17L2.5 13.5C2.3 12.9 2.6 12.4 3.1 12L6.4 8.7C6.8 8.2 7.3 8 7.8 8C8.3 8 8.6 8.1 8.9 8.3L11.2 10.6M24 11.9H22V8.5L20.2 7.8L21.1 12.2L22.1 17.4L23 21.8H20.9L19.1 13.8L17 15.8V21.8H15V14.3L17.1 12.3L16.5 9.3C15.9 9.9 15.2 10.5 14.4 10.9C13.5 10.8 12.6 10.4 11.9 9.7C13.5 9.4 14.6 8.6 15.3 7.4L16.3 5.8C16.9 4.8 17.8 4.5 18.9 5L24 7.2V11.9M11.4 4.4C12.5 4.4 13.4 5.3 13.4 6.4C13.4 7.5 12.5 8.4 11.4 8.4C10.3 8.4 9.4 7.5 9.4 6.4C9.4 5.3 10.3 4.4 11.4 4.4M16.5 .3C17.6 .3 18.5 1.2 18.5 2.3C18.5 3.4 17.6 4.3 16.5 4.3C15.4 4.3 14.5 3.4 14.5 2.3C14.5 1.2 15.4 .3 16.5 .3Z" style="fill: currentcolor;"></path>
    </svg>
  </span>
  <span class="k-button-text">Target Weak Spot</span>
</button>
<button class="k-button k-button-md k-button-rectangle k-button-solid k-button-solid-base k-rounded-md">
  <span role="presentation" class="k-button-icon k-icon">
    <span role="img" aria-label="poop">💩</span>
  </span>
  <span class="k-button-text">Bio Weapon</span>
</button>

We currently keep an image library for our customers where we allow them to upload images for use in the editor. Our existing implementation uses something called tinymce and MoxieManager. I see that the jQuery implementation has something similar, but it is not included in the react toolset. 

Can we get the ImageBrowser / FileBrowser part of the jQuery Kendo ported over to the react version?

I have attached an image for example.

Hi we are wanting to use the scheduler and control the display of overlapping items differently than the default.  Are there any resources you could point me to that explain how two items scheduled over the same time interact or can be customized?

If we wanted for the items to be z-indexed over each other instead of shown side-by-side, is that possible?

Hi Team, 

###Current Behavior

When displaying checkboxes, they are not aligned for nodes with children vs. nodes without children

### Example

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

### Expected Behaviour

Nodes checkboxes should be aligned the same regardless of if they have children.

###Version

4.8.0

Thanks and Kind Regards,
Grant

I'd really like a KeepIt prop on https://www.telerik.com/kendo-react-ui/components/conversationalui/api/Action/ so that the action stays even when someone is typing or there is another message below it.

The use case would be a link to a Order # for example that they could go back to and click.

https://www.telerik.com/kendo-react-ui/components/conversationalui/suggested-actions/

Example of how this works with react-native-gifted-chat:

https://github.com/FaridSafi/react-native-gifted-chat#message-object

A horizontal scroller or scroll list?  A list of items or chips can be scrolled through horizontally, either by using arrow buttons or drag.

This is a common way of accessing a long list of items on a phone - by swiping left or right on the list with your finger.

There are a couple of horizontal scroller controls available for react - but they are not complete, buggy and not supported.