Description
PivotGrid does can not export all the date to excel when the nodes are collapsed
Plan
KendoReact Free
Steps To Reproduce
https://www.telerik.com/kendo-react-ui/components/pivotgrid/excel
Configure a PivotGrid with multiple row and column fields, and at least one measure.
Expand only a few nodes manually.
Click the Export to Excel button.
The exported file contains only the visible/expanded rows/columns.
Screenshots or video
No response
Actual Behavior
It is not practical or user-friendly to expect users to manually expand every node (especially if data changes frequently).
Users expect complete data export based on the selected dimensions/measures and based on provided data source to generate pivot grid — not just what is visible.
Expected Behavior
Expected Behavior:
When clicking Export to Excel, PivotGrid the entire dataset should be exported in expanded format.
Browser
Chrome, All
Browser version
latest
OS type
MacOS
OS version
No response
Last working version of the KendoReact package (if regression).
No response
Any help would be appreciated.
When there are many items in the menu, the height should not exceed the page size. Now the scroll is not displayed.
https://stackblitz.com/edit/react-kxderjef
It refers to version 9.1.0, version 8.5.5 works fine
Thank you
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:
Hi, there is a problem with filter filter popups in Data Grid.
Steps to reproduce:
1. Go to https://www.telerik.com/kendo-react-ui/components/grid/filtering
2. Open the date filter popup in the "FirstOrderOn" Column and click on any date
3. Open and close the filter combo in "Disconinued" column couple of times.
Actual Behavior
On version 9.1.0 besides Opening the "Disconinued" filter combo, the date popup also openes. On version 8.5.0 seems to work fine
Expected Behavior
Only the popup from "Discontinued" column should be Opened / Closed
Chrome
Browser version
131.0.6778.205
OS type
Windows11
- open answers.microsoft.com/en-us/msoffice/ using valid credentials.
- Navigate to any article link and hit enter.
- Select 'reply' button.
- Navigate to 'format' list and invoke it.
- Now Run the fast pass using Accessibility Insights for web and observe the failure 'aria input field name'.
Aria input field doesn’t have an accessible name.
Ensure every aria input field should have an accessible name.
User Impact:
We use data grids with virtual scrolling for inline editing a large number of records. However, when we want to add a new row to the grid it automatically resets the scroll position and doesn't even fire onPageChange event so the records you see do not correspond to the scroll position.
Check the following example (scroll to bottom, click anywhere on the table - this will add a new row - and observe the described problem):
https://stackblitz.com/edit/react-52zzvz?file=app%2Fapp.tsx%3AL78
Test Environment:
OS: Windows_11Screen Reader: NVDA (2021.3)
Repro Steps:
1. Open URL: SMB Scheduler (agentcalendardevone.azurewebsites.net) page in Edge Browser.
7. Observe an issue that Incorrect role 'link' is defined on button controls.
Actual Behavior:
Incorrect role 'link' is defined on button controls present on 'Calendar' popup.
Expected Behavior:
In this case, the expected role is {button}. All components need a proper role attribute, ideally with semantics. In rare cases a role attribute should be added to give full context and information to assistive technology. Learn more by reading about when to use an aria role and the html/aria role mappings.
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.
Expected Result:
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.
Screenshot attachment:
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
- This issue is observed with all three screen readers.
- Same issue is observed in chrome browser as well.
- Turn on Screen Readers:
- Narrator: Win + Shift + Enter
- NVDA: Ctrl + Alt + N
- JAWS: Ctrl + Alt + J
- Verbosity:
- Narrator: Default
- JAWS: Beginner, Highest
- NVDA: Default
- Open the URL: Agora Home Page (PPE) in latest edge browser.
- Press tab key to move to the 'Save as' control present in the page and activate it using enter key.
- Save as dialog gets displayed.
- Press tab key to move to the 'workspace to be saved as in' edit field and activate it using 'Alt + down arrow key'.
- Enter any invalid data in the search edit field.
- Now Verify whether screen reader is announcing the search result information on giving invalid data in the search edit field in windows or not.
- This issue is observed with all three screen readers.
- Same issue is observed in chrome browser as well.
- Name is not properly defined for once control. Screen reader is narrating the name twice for the once control as "Once check box not checked report frequency: once"
Path: Home > Header > Reports > Schedule a report button > Schedule a Report pop-up.
Refer Attachment: Name is not properly defined for once control.png
- Turn on Screen Readers:
- Narrator: Win + Shift + Enter
- NVDA: Ctrl + Alt + N
- JAWS: Ctrl + Alt + J
- Verbosity:
- Narrator: Default
- JAWS: Beginner, Highest
- NVDA: Default
- Open the URL: Agora Home Page (PPE) in latest edge browser.
- Press tab key to move to the 'Alerts' control present in the page and activate it using enter key.
- 'Alert Definitions' page gets displayed.
- Press tab key to move to the 'Functions? Filter' control and activate it using 'Enter key'.
- Navigate through the radio buttons in the displayed popup using arrow keys and verify whether screen reader is announcing incorrect name for the radio buttons present in the filter dropdown in windows or not.
- This issue is observed with (NVDA, JAWS and Narrator) using down arrow key/Tab key.
- Press F12 key to open the developer tool and inspect the code.
- Open URL: https://demos.telerik.com/kendo-ui/grid/filter-menu-customization in Edge browser.
- Navigate to the Filter icon present in the city/Title/Birth date column header.
- Press F12 to open Dev tool and inspect the code for Filter button.
- Observe whether correct role is defined for "Filter" button or not.
- Same issue is observed for the below two dialogs.
- Visually appearing heading 'Import Workspace' is not defined as heading programmatically. [Path: Home page-->activate 'Hamburger' menu-->Import workspace--> Popup] (Refer Attachment: Note_1_Visually appearing heading 'Create Workspace' is not defined as heading.png.)
- Visually appearing heading 'Create Workspace' is not defined as heading programmatically. [Path: Home page-->activate 'Hamburger' menu-->Add new workspace--> Popup] (Refer Attachment: Note_2_Visually appearing heading 'Import Workspace' is not defined as heading.mp4).
- Turn on Accessibility insights for web extension.
- Navigate to the headings toggle control and turn it on.
- Open the URL: Agora Home Page (PPE) in latest edge browser.
- 'Agora home page (PPE)' will be displayed.
- Navigate to 'Add a widget' control using tab key and activate it using enter key.
- Navigate to 'Mark down' control in the list displayed using tab key and activate it using enter key.
- 'Create text widget' dialog gets displayed.
- Observe and verify whether visually appearing heading text 'Create Text Widget' is programmatically defined as heading or not.
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.
On this page: https://www.telerik.com/kendo-react-ui/getting-started/
On this section: "Add a KendoReact Data Grid"
When I launch the app as usual:
```sh
yarn start
```
Then the browser page includes this error:
```
Compiled with problems:
ERROR in ./.yarn/__virtual__/@progress-kendo-react-data-tools-virtual-df92d36fcf/0/cache/@progress-kendo-react-data-tools-npm-5.2.0-8d098f65a0-5d68752aaa.zip/node_modules/@progress/kendo-react-data-tools/dist/es/columnmenu/ColumnMenuFilterForm.js 19:0-55
Module not found: Error: @progress/kendo-react-data-tools tried to access @progress/kendo-react-buttons (a peer dependency) but it isn't provided by your application; this makes the require call ambiguous and unsound.
Required package: @progress/kendo-react-buttons
Required by: @progress/kendo-react-data-tools@virtual:79c9c696d5f1e6f4dd730946c0d2912611551a498926b146bcbdd9d142588c5f4c2333469b63e7a9a2bdd1f0f1313d0d70b72cc8dbcafcc20e21e6b9790f6068#npm:5.2.0 (via /Users/joel/git/joelparkerhenderson/demo/demo-react-kendo/.yarn/__virtual__/@progress-kendo-react-data-tools-virtual-df92d36fcf/0/cache/@progress-kendo-react-data-tools-npm-5.2.0-8d098f65a0-5d68752aaa.zip/node_modules/@progress/kendo-react-data-tools/dist/es/columnmenu/)
Ancestor breaking the chain: demo-react-kendo@workspace:.
…
```
The solution that works for me...
Add the package:
```sh
yarn add @progress/kendo-react-popup
````
Edit `src/App.js` and add this line:
```js
import '@progress/kendo-react-popup';
```
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.
Hi,
I have run into an issue when trying to input a date value where its parts contain a leading 0. The autoCorrectPaths option is set to false and I have specified a date format in my datePicker component.
Reproduction:
1. open https://stackblitz.com/edit/react-wz6zocpe?file=app%2Fapp.jsx
2. try to input a date by typing 09, then 03, then 2025
Expected behaviour:
The date in the input field should be "09.03.2025"
Actual behaviour:
The date in the input field is "day.09.2000"