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.
It should have the following functionalities:
Please add the “add widget” functionality as the jQuery version has.
Please add the “remove widget” functionality as the jQuery version has.
I have the following Feature Request:
### Current Behavior
When the 'disabled' attribute is true for a TreeView node, the entire node is disabled, preventing the user from selecting, expanding and checking.
### Desired Behavior
To be able to specify what functionality of the node to disable, select and/or expand and/or check or all.
### Use case
1) A TreeView displays a list of Countries that when;
1.1) expanded, displays a list of provinces as items.
1.2) selected, filters a list of cities in a different component by the selected node (country or province)
1.3) checked, indicates business coverage for that region.
My use case dictates that once an area has been checked it cannot be unchecked. But the same node whose checked state must be disabled, still needs to be expandable and selectable for the above reasons, for viewing purposes.
I can't find anything on your website or on the internet that explains how to navigate a Kendo React ListBox control using the keyboard.
Can you point me in the right direction on this issue?
I am using the date range picker component and it works fine.
But I want to add time select feature to date range picker.
I did not see this feature when I examined the document.
Please your support
Please add down arrow to multi-select dropdown similar to combobox or dropdownlist.
When displaying checkboxes, they are not aligned for nodes with children vs. nodes without children
### Expected Behaviour
Nodes checkboxes should be aligned the same regardless of if they have children.
Thanks and Kind Regards,
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?
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:
Let me know if any other concerns or ideas around this may arise.
I've noticed in your other products, the dropdownlists have a property that allows for grouping sets of data.
What would it take to get that included in Kendo UI React?
We have a use case that this would be very helpful.
We are currently developing an application based on Kendo React components.
We are wondering if the React-Gantt chart has the functionality to edit the data by drag-n-drop the same way it possible with JQuery-Gantt (see attachment).
Thanks in advance for your help.
Add more animation options to the KendoReact Chart rendering.
For example, we can add the following type of animation:
The new suggested animation type should change smoothly the Y values of the line, that is an animation of the line from its old points to its new points."
This should result in the lines (series) animating not the entire Chart.
MaterialUI exposes a `ListBoxComponent` prop on their dropdown components (https://material-ui.com/api/autocomplete/) it would be nice to have that exposed on the kendo multiselect as well.
Use cases include:
Aria label attribute is not defined for button in 'Insert image' dialogue.
Narrator is announcing as 'No file chosen, choose file, button'.
Aria label attribute should be defined for button in 'Insert image' dialogue.
Adding effective form labels is absolutely necessary to make forms accessible. The purpose of form elements such as a checkboxes, radio buttons, input fields, etc. is often clear for sighted users, even if the form element is not programmatically labeled. This isn't usually the case for screen reader users. Adding a label to all form elements eliminates ambiguity and contributes to a more accessible product.
Interactive control elements have focusable descendants.
When interactive elements have an incorrect name and role, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content. Knowing the role for a control helps users know what will happen when that object has focus and is selected, as well as what keyboard shortcuts to use when interacting with the control.