1) Use this StackBlitz application: https://react-scwx3i.stackblitz.io - This is based on Telerik's own DatePicker React example.
2) Highlight the AM/PM section.
3) Try to change the AM/PM section via typing. It doesn't change. Note that other fields in the date/time picker are responsive to keyboard input.
Expectation is that the AM/PM section should respect at least "A" and "P" inputs.
https://www.telerik.com/kendo-react-ui/components/charts/api/GridLines/
Similar to how other elements provide the option to render a custom visual.
Hi
I noticed in the PDF Export component limitations (https://www.telerik.com/kendo-react-ui/components/drawing/limitations-browser-support/) that it does not support iFrames. This is a major issue for us as we have data containing full HTML markup and <style> tags, which we want to embed in a PDF. We need to use an iFrame otherwise the styles will bleed into the rest of the document. Is there any plans to support iFrames in the future?
Defined a date rang. But it allows to enter a date larger than a max date of the range. Both via calendar and manually.
const minDate = new Date(1, 1, 1);
const maxDate = new Date(9999, 12, 31);
return (
<DatePicker value = {this.state.value}
min={minDate}
max={maxDate}
/>
The KendoReact MaskedTextBox value cannot be cleared once a value is set. See this forum post for examples and a proposed workaround: https://www.telerik.com/forums/maskedtextbox-cannot-be-cleared
I would like for a user to be able to clear the MaskedTextBox value without having to code it as a special case in the onChange event handler. I believe this should be done by default as per the Kendo jQuery MaskedTextBox, but it could also be optional via a prop or clear button.
I am trying to create a radial gauge with gradient fill but I don't see any help regarding this. Please see the below image of what actually I am looking for.
Hi Team,
We are using Kendo react scheduler in one of our project. We need a custom marker in a scheduler control similar to current date time marker in a Timeline view. I have attached the image for reference.
Please let us know if there is any property available or any other ways to achieve this functionality. Also, how can we place it properly in a scheduler slot based on specific date and time like May 12, 2020 13:40.
Regards,
Abhinav
Description of the problem
In the Grid component with infinite scrolling, when a user scrolls down, the grid will bounce them back up to the first row when loading the next couple of rows. We get this same behavior in our application so it doesn't seem to be a mistake in the demo. We've encountered this issue in both version 1.x and the most recent version of Kendo.
To reproduce:
- go to the demo for this component;
- slowly scroll down in the grid component.
Code, screenshots, etc
Since this is also broken in the docs, I don't think it's necessary to add screenshots or code.
Currently, the TabStrip has a built-in Fade animation.
We provide a property to allow setting different types of animations like Slide, Push etc.
Currently, it only gets the value and the name of the Field:
https://www.telerik.com/kendo-react-ui/components/form/api/FieldValidatorType/
Actual Result:
While navigating in table, Narrator is not announcing as 'enter table' and it is also not announcing rows and column information. while navigating in table, With arrow keys or table navigation keys or tab key, Narrator is announcing as 'end of line/blank'.
With caps-arrow keys, Narrator is giving row and column information.
Expected
While navigating in table, Narrator should announce as enter table and it should also give row and column information. And while navigating with arrow keys or table navigation keys or tab key, Narrator should not announce as 'end of line/blank' instead it should give row or column information
Actual results:
aria-label is not defined for ‘Reply editor’ when the keyboard focus is on 'Reply’ edit box narrator is announcing as “Editing End of line”.
Expected
All components need an accessible name, ideally using semantic elements and attributes. In rare cases, aria-label or aria-labelled by may be needed to alter the name. Learn more by reading about the accessible name property.
User Impact
When interactive elements have an incorrect name, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content.
- open the given URL using valid credentials.
- Select 'reply' button.
- Now Run the fast pass using Accessibility Insights for web and observe the failure aria required children.
Actual results:
Elements with Aria role is not containing child role with in them.
Expected results:
Elements with Aria role should contain child role with in them.
User Impact:
For each role, WAI-ARIA explicitly defines which child and parent roles are allowable and/or required. ARIA roles missing required child roles will not be able to perform the accessibility functions intended by the developer.
- open the given URL using valid credentials.
- Navigate to 'Reply' button and invoke it.
- Navigate to 'insert image' button and invoke it.
- Now, try to upload the image and observe
Actual Result:
User is unable to navigate to 'upload' button in 'insert image' dialogue. On invoking 'insert image' dialogue focus is navigating in the background and after navigating whole page then focus is going to the 'insert image' dialogue. Now, when user try to upload the image, focus is going out of the dialogue (going to the top of the page).
Expected Result:
When focus order does not follow the visible reading order, the experience can create a different interaction pattern, and/or unintended content relationships for assistive technology users. On rare occasions, there is a logical reason the focus order is different from the reading order, but the meaning of the content and interactions must remain the same.
This could be done as a demo, that showcases how this functionality can be added and extended for more elements.
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:
- simplifying styling
- Custom scroll bars for the dropdown