Dear Sir/Madam,
We are piloting our application and repeatedly get the same feedback from our users: they find entering information in the date and time inputs annoying.
The reason for this is that they have to enter a date (say 1 december 2024) by entering:
Instead, they would like to enter a date in one go, say
Likewise, they would enter times like "1005" for "10:05". Now they have to enter ":" to go to the minutes field.
We would like to respond to their feedback, but don't know to implement this. Is this something that Kendo supports? If not, we are willing to pay to give this feature request priority. Could you help us out?
Regards,
Peter
To demonstrate:
1. Open your simplest interactivity/selection demo, which is not grouped, in StackBlitz. See: https://www.telerik.com/kendo-react-ui/components/grid/interactivity/selection/
2. Add the Grid's group prop. To demonstrate the bug nothing else needs changed
<Grid group={[]} ...
3. Run demo, scroll down and pick a row.
4. Observe the grid scrolls to the top and you cannot see your selected row unless you scroll back.
Hi!
I have noticed that keyboard navigation doesn't work in the filter editor components inside the Filter component
Reproduction:
Is there a way to enable it or go around it?
Actual results:
Aria label attribute is not defined for button in 'Insert image' dialogue.
Narrator is announcing as 'No file chosen, choose file, button'.
Expected results:
Aria label attribute should be defined for button in 'Insert image' dialogue.
User Impact:
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.
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
Looking at the JSDoc for for `toDataSourceRequestString` and `toDataSourceRequest`, they both appear to have JSDoc above them, showing the parameter as:
* @param {DataRequestState} state - The state that will be serialized.
Should this actually have `@param {DataSourceRequestState}`?
Given the simple example:
const RatingContainer = () => {
const [ratingValue, setRatingValue] = useState(0);
const clearRating = () => {
setRatingValue(0);
}
const onRatingChange = (event) => {
setRatingValue(event.value);
}
return <div>
<Rating
value={ratingValue}
onChange={onRatingChange}
/>
<Button
onClick={clearRating}
>
Clear
</Button>
</div>
}
export default RatingContainer;
The Rating component behaves as expected when updating `ratingValue` through the Rating component. However, when I want to clear the rating value with the 'Clear' button to update the `ratingValue`, the number of stars displayed doesn't update reflect the value of `ratingValue`.
Here is a subsection of my package.json file.
"@progress/kendo-data-query": "^1.6.0",
"@progress/kendo-drawing": "^1.17.5",
"@progress/kendo-licensing": "^1.3.0",
"@progress/kendo-react-animation": "^5.13.0",
"@progress/kendo-react-buttons": "^5.13.0",
"@progress/kendo-react-charts": "^5.13.0",
"@progress/kendo-react-common": "^5.13.0",
"@progress/kendo-react-data-tools": "^5.13.0",
"@progress/kendo-react-dateinputs": "^5.13.0",
"@progress/kendo-react-dialogs": "^5.13.0",
"@progress/kendo-react-dropdowns": "^5.13.0",
"@progress/kendo-react-editor": "^5.13.0",
"@progress/kendo-react-excel-export": "^5.13.0",
"@progress/kendo-react-form": "^5.13.0",
"@progress/kendo-react-grid": "^5.13.0",
"@progress/kendo-react-indicators": "^5.13.0",
"@progress/kendo-react-inputs": "^5.13.0",
"@progress/kendo-react-intl": "^5.13.0",
"@progress/kendo-react-labels": "^5.13.0",
"@progress/kendo-react-layout": "^5.13.0",
"@progress/kendo-react-listview": "^5.13.0",
"@progress/kendo-react-notification": "^5.13.0",
"@progress/kendo-react-pdf": "^5.13.0",
"@progress/kendo-react-progressbars": "^5.13.0",
"@progress/kendo-react-tooltip": "^5.13.0",
"@progress/kendo-react-treelist": "^5.13.0",
"@progress/kendo-react-treeview": "^5.13.0",
"@progress/kendo-react-upload": "^5.13.0",
"@progress/kendo-svg-icons": "1.4.2",
"@progress/kendo-theme-bootstrap": "^5.2.0",
Controlled TextaArea componenet with autoSize and rows properties.
const App = () => {
const [state, setState] = useState();
return (
<TextArea
value={state}
onChange={(e) => setState(e.value)}
autoSize={true}
rows={2}
/>
);
};
Add couple text lines to extend TextArea size and remove these empty lines in any way
Content from TextArea field is removed but TextArea height stays the same, doesn't come back to it's initial value. It's different comparing to example from your docs where example contains uncontrolled component.
Controlled TextaArea componenet with autoSize and rows properties.
const App = () => {
const [state, setState] = useState();
return (
<TextArea
value={state}
onChange={(e) => setState(e.value)}
autoSize={true}
rows={4}
/>
);
};
and styles like these
.k-textarea textarea {
border: 1px solid blue;
}
Start typing anything
Height of textarea component is decreasing
Setting the stage prop to "DEFAULT" does not update the Window component as expected:
const [stage, setStage] = React.useState<string>('DEFAULT');
const handleStageChange = (e: WindowActionsEvent) => {
setStage('DEFAULT');
};
<Window
stage={stage}
onStageChange={handleStageChange}
There is a bug when rendering nested `PanelBarItem` components into a `PanelBar`. This error began in version 8.0 and still exists in 8.2.0.
In the linked example sandbox, you can see that I am rendering an empty array of children and it causes an error. This used to not cause any issues.
An empty array is needed because we render some `PanelBarItems` that come from an AJAX query and so the children starts off as an empty array until the requests completes.
Thank you,
Ryan