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.

The DatePicker and DateInput React components miss the customizable button to clear the date value.

Would be nice to have ability to customize the icon, size, margins and a selectable option to clear the date value to null or a default value (as set to the component) or bind a custom event handler.

Hi Team,

I am writing to inquire about modifying the default behaviour of the Kendo UI Menu component. The sub-menu items are displayed when hovering over the parent menu item. However, I require the sub-menu items to be visible only when the parent menu item is clicked.

Desired Behavior:

Sub-menu items should remain hidden by default.
Clicking on the parent menu item should expand the sub-menu and display the child items.
Clicking on another parent menu item should collapse the previously expanded sub-menu and expand the new one.
Implementation Challenges:

I have explored the Kendo UI documentation and API, but I am unable to find a direct configuration option to achieve this desired behaviour.

Could you please provide guidance on how to modify the Kendo UI Menu component to display sub-menu items only on click of the parent menu item?

Please let me know if you require any further information or if there are any examples available that demonstrate this functionality.

Reference URL - https://stackblitz.com/edit/react-zugkrezk?file=app%2Fapp.jsx,app%2Fapp.css 
Reference Ticket - https://www.telerik.com/account/support-center/view-ticket/1679073 

Thank you for your time and assistance.
Mahesh

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

When typing into a date picker and trying to type Feb 29th, 2024 (or any other leap year ofc) the date is updated incorrectly by the kendo date picker validation. As the user types the year their previous entry of 29 is updated to 28. This should update check should probably not occur until the user is done updating the input. If there is some fix or workaround we can do on our end to resolve this issue please let us know

Here's a video of the bug in our application

However, I was also able to reproduce the exact same behavior even in the documentation:

As stated in the subject. To reproduce:

• Create a blank react project as per the KendoReact Data Grid Getting Started documentation e.g.

npx create-react-app my-app --template typescript

• Change the react and react-dom dependencies in the generated package.json file from ^19.0.0 to ^18.0.0, add corresponding "@types/react": "^18.0.0" and "@types/react-dom": "^18.0.0" entries to devDependencies, and add a standard tsconfig.json file e.g.

{
    "compilerOptions": {
      "target": "es6",
      "lib": [
        "dom",
        "dom.iterable",
        "esnext"
      ],
      "allowJs": true,
      "skipLibCheck": true,
      "esModuleInterop": true,
      "allowSyntheticDefaultImports": true,
      "strict": true,
      "forceConsistentCasingInFileNames": true,
      "noFallthroughCasesInSwitch": true,
      "module": "esnext",
      "moduleResolution": "node",
      "resolveJsonModule": true,
      "isolatedModules": true,
      "noEmit": true,
      "jsx": "react-jsx"
    },
    "include": [
      "src"
    ]
  }

• Install required @progress packages as per the KendoReact Data Grid Getting Started documentation e.g.

npm i @progress/kendo-react-grid @progress/kendo-data-query @progress/kendo-react-data-tools @progress/kendo-react-inputs @progress/kendo-react-intl @progress/kendo-react-dropdowns @progress/kendo-react-dateinputs @progress/kendo-drawing @progress/kendo-react-animation @progress/kendo-licensing @progress/kendo-react-buttons @progress/kendo-react-treeview @progress/kendo-react-popup @progress/kendo-svg-icons @progress/kendo-theme-default

• Delete content generated by create-react-app which is not required e.g. App.test.tsx, logo.svg, reportWebVitals.ts, setupTests.ts and corresponding references
• Confirm you can run npm start with no webpack errors or warnings (see screenshot)
• Add a <Grid> with <GridNoRecords> to App.tsx e.g.

    <div className="App">
      <header className="App-header">
        <Grid>
          <GridNoRecords>This generates TS2786</GridNoRecords>
        </Grid>
      </header>
    </div>

Confirm that npm start results in error TS2786 (see screenshot).

Please see attached for the sample project (with the node_modules folder removed). I believe this error was introduced in v9.0.0 as part of the migration from classes to functional components.

in latest v9.3.1 it appears GridFilterCell isn't passing properties shaped as 'isRequired' on DatePicker popupSettings 

this does seem to be a regression because i just recently noticed it in latest upgrade which we need for other bug fixes.

i pursued patching myself by populating animate in GridFilterCell.mjs which seemed to work but then i got warning for the next required property "appendTo". however, populating appendTo yields warning "Warning: Failed prop type: Invalid prop `appendTo` supplied to `Kendo React Popup`. Validation failed." so it's not easily reconcilable that way... therefore i tried removing isRequired on all 3 DatePicker popupSettings properties which of course avoided warnings and i didn't see any negative side effects.

here is a codesandbox repro minimally tweaked to include a date field from kendo grid's "getting started" demo: https://codesandbox.io/p/sandbox/cool-sanne-d4tp85

admittedly this is just a warning but it does create unnecessary noise in browser debug which detracts from issues truly requiring attention during development.

screenshot with the warning from that demo repro:

We are using a customized ChartToolTip with button in our bar chart. However the tab order is not correct for multiple charts. The expect behavior we were told by our accessibility testing team is first chart -> button on tooltip -> second chart -> button on tooltip and so on. The actual behavior is tab shortcut will switch between charts then back to the first chart tooltip element. 

@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.

When I press on a day from the past the DatePicker automatically scrolls to the next/previous year. Please check the attached video. 

Is there any workaround for this issue ?