KendoReact Editor not working in NextJS application.
This is the error:
ReferenceError: navigator is not defined.
The error can be reproduced in our NextJS application as well when adding the Editor component.
The error may occur due to this line:
const firefox = /Firefox/.test(navigator.userAgent);
Whether the Treelist supports multi column headers ,Nest columns in the columns definition?
Like the Grid
https://www.telerik.com/kendo-react-ui/components/grid/columns/headers/
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.
i am using KendoReact Drawdom version 1.5.12
I have some input elements for uploading images, and showing the a preview of uploaded image.
I want to export a PDF version of the form, but drawDom.cloneNodes() throws an exception when handling input elements of type file. that is because these type of input elements can not have value attribute.
On your Grid Demos: When ever you try to edit a text cell the cursor always goes to the end of the text box
For example, go to your demo:
https://www.telerik.com/kendo-react-ui/components/grid/editing/editing-inline/
- Edit the first row. Try to type something before "Chai" - the cursor will jump to the end of the textbox
Hi,
the current filter is great but a little bit difficult to use. I would like to see an inline filter like the following screenshot:
It is used by many applications. Just to name a few
* Gitlab (where the screenshot is from)
* Contentful (CMS)
* Google Cloud Console
Hi
Please add SignalR support for grid and other controls similar to Kendo UI for jQuery.
Thank you
Hello,
We need to create a DateTime Picker with max and min limit on Date and also Time.
Currently, the range works as of 22/09/2019 5:30 AM to 21/09/2020 5:30 PM, where complete 24 hrs is been selectable.
We need the time range to be restricted per day. For instance, in the above example, it should be 5:30 AM to 5:30 PM per day from 22/09/2019 till 22/09/2020.
Thanks in advance.
Expected:
Narrator shouldn't be mute , keyboard focus and narrator focus should be in sync and narrator should announce the info about the menu items clearly
User Impact:
Users with visual impairment who rely on screen readers will face difficulties if narrator is not announcing any information about the menu items present in combo box while navigating through them.
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
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,
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.
Repro:
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'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?
Actual results:
Expected results:
Interactive control elements have focusable descendants.
User Impact:
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.
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.
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.