in the provided video, an example of the unordered list has been taken up. But the same is applicable to the numbered list as well.

When a user tries to add a new point to an unordered list in a new line and then clicks the backspace, the unordered list remains. Pressing 'Enter' to start a new line shows the unordered list bullet points again.

Can we update it so that on   Pressing backspace to remove the unordered/ordered list should delete it entirely and should not leave any highlighting in the description box editor field.

video : https://www.loom.com/share/480debbe4f2648339ecb80cd9b6ed853?sid=3914f5dc-f477-4afd-a55d-df4a26603da7   

please go through video where i have provided , example of current behavior and expected behavior 

Test Environment:

Environment Details:
OS: Windows11 version 21H2 (OS build 22000.856)
Edge Browser version: 104.0.1293.47

Repro steps:
1. Open Code Pen: https://codepen.io/m1mrt/pen/VwXjEzJ page in Edge Browser.2. Run Axe dev tools3. Observe an issue that select element has an accessible name.

Actual Result:Select element does not have an accessible name.

We have problems with the grid because for no reason a 'display:none' appears, specifically in this creation action

We can't understand when the error might occur, we think it's a coincidence of class names.

Can you guide us through this error?

I have attached files, in which there is an app bar content there is a dropdown in the dropdown there are four elements, in that I need four drawer container on the left side as I attached by clicking the single dropdown, how can I attach 4 drawer container in a single project 

Thank you

1. Turn on Accessibility insights for web extension.
2. Navigate to the headings toggle control and turn it on.

Environment (OS, Application, Versions)

Repro Steps

1. Open URL: Column Menu - Kendo React (telerik.com)
2. Navigate to context menu controls available on column headers of Basic usage table.
3. Verify if context menu is accessible using keyboard.

Actual Results

The 'context menu' controls available on the column headers under the basic usage table are not accessible using the keyboard.

Expected Results

The 'context menu' controls available on the column headers under the basic usage table should be accessible using the keyboard.

I have noticed that whenever you want to upload multiple photos at once, using this React Upload Component & Events - KendoReact Docs & Demos (telerik.com) component the previews of the images uploaded bounce/ shake around. I've tried this on multiple browsers and they all have the same bouncing effect for the image previews. For a single photo it doesn't do it but once multiple images are added, it will do it.

As per the subject. This can be observed in the following StackBlitz which is forked from the Telerik documentation on resizing with three small changes:

• Remove style={{ height: '400px' }} from the Grid component in app.tsx
• Remove height: 100%; from my-app style in index.html
• Remove height: 100%; from html, body style in index.html

https://stackblitz.com/edit/react-vajzshwv?file=app%2Fapp.tsx,index.html

Logged as a bug because there is nothing in the documentation stating that a height for the Grid or Grid container must be set in order for this to work. If this is a documentation issue rather than a code issue, please advise the recommended approach for using the Grid resizable property.

@progress/kendo-react-inputs@9.0.0

going back to this ticket, we'd like to use CTRL+up/down for our own purposes... as such, you can now disregard that feature request in lieu of fixing this bug =)

since this is undocumented behavior (documentation screenshot below) i believe we have a legitimate bug claim.

also, other controls like DateTimePicker reliably ignore the CTRL+up/down while implementing bare up/down as documented.

Hello,

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.

Kind regards,
Sergei

Hi Team,

We are using data-grid along with excel export for showing lakhs of data (sometimes over 20 lakhs) in our app and over 80 columns.  We found a the TIME TAKEN is over 2.5 mins for over 10 lakhs (rows*cols) data. We have tried the KendoOmxml with kendo saveAs function from file-saver as well.

I have tried with server-side export instead of client-side aslo and still it's the same behavior. In my observation I am suspecting the below line. 

 component.toDataUrl().then((dataURL) => {

Here component is the reference of ExportExcel component. After getting dataURL I am calling save api to download the file. But toDataUrl() function is taking the whole time. Is there any way we can get this base64 dataURL faster?

You can refer to the codeSandbox Link. We have 80 columns(including duplicates), while importing productsSmall.json file which contains 77 rows, export excel is working well and good. But when you change the import to productsLarge.json file which contains 10,000 rows (if cannot be seen, please copy paste the dummy data from attached file with even more usual amount of data we use in our app), the screen is stuck or takes too much time to get process complete and sometimes it throws error(maybe because of codesandbox incapability).

Stackblitz link (if codesandbox hangs more) https://stackblitz.com/edit/react-q5wlpg-4bs2zc?file=app%2Fmain.tsx

We have a large number of customers requesting this feature to be fast. Please let us know with an optimized solution. 

Regards,

Manjula

Drag-and-Drop editing is a very usefull and required functionality in a lot of enterprise apps (Move/resize tasks along the timeline, adjust completion percentage, dependencies editing).
We noticed these features are (maybe partially) available in the Kendo Gantt components for (at least) jQuery and Angular.
Are there plans to introduce similar functionality in the KendoReact Gantt component? If so, could you share a timeline for implementation? Or maybe you can suggest some workarounds? 

We’d greatly appreciate your insights on this point, as it's critical to our evaluation process.