Custom editors are great! But often when you have a custom editor, you want to restrict data entry to only use that editor, and not free-form typing in the cell. You can prevent free-form typing in the cell by disabling the cell, but then the custom editor button is no longer available. Suggestion is to still show custom editor button even if cell is disabled, perhaps with an additional setting; so that you could optionally not show the custom editor if the cell is disabled, since often a disabled cell should prevent any kind of modification.
Currently the spreadsheet dynamically creates the FilterMenu for a range, that is, it's not created until someone clicks the filter dropdown, and it's destroyed if they switched tabs. There is no event that is fired when these things happen, which makes it hard to attach to, and customize, the FilterMenu without setting up some crazy listening code (setTimeout, etc.). It would be great if either (or both: - You could specify a template for the filter menu. - You could listen for a "FilterMenu Initialized" event and capture the menu there and customize it.
In MS Excel when you type a number you can easily go to other cells by using the arrow keys and type in another number, thus allowing for fast editing of the spreadsheet. This does not work in the spreadsheet component. this functionality only needs to work when not creating a formula.
The Excel file downloaded from Spreadsheet does not maintain leading spaces. In other words, the internal sharedString.xml should use <t xml:space="preserve"> when necessary.
I use data binding data source for spreadsheet But when I use it, data auto input begins at row 0 I want to insert 2 row (To Write title)
DefaultCellStyle property in spreadsheet has a field “Wrap”, but doesn’t have a field “Format”. For example, if I need to process all cells as text, I must set the field “Format” on a client side: sheet.range("A1:AX200").wrap(true).format("@"); It works. But the initialization of the range ("A1:AX200") takes time… It is not very fast… It would be better to have the field “Format” in the DefaultCellStyle property in spreadsheet…
Presently in Spreadsheet tooltip is not working for filter applied range so tooltip should display for each cell in which the range of filter is applied
Currently if you access cells range programmatically, you can set background color, text color etc. It would be good to have the way to set classes or to get the DOM of the range. Another option would be to get DOM or set a class to individual cells (e.g. via range.forEachCell).
Wanting to format a subset of a single cell with text styling different from the rest of the cell contents. Something like the following:
or
The current client-side export functionality does not preserve the number of columns.
Load the following file in the Spreadsheet which contains columns up to "BA".
Export the file
Load the file again in the Spreadsheet and notice that the columns are displayed up to "AX" instead of "BA".
Client-side export does not preserve the number of columns greater than "AX".
Client-side export does not preserve the exact number of columns.
When a cell/row is selected, its first cell is focused and the sheet is scrolled to show it. If a long sheet is scrolled down/right to edit cells, this scroll top/left is very annoying and user unfriendly.
In these scenarios Excel focuses the topmost/leftmost currently visible cell, avoiding sheet scrolling.
NOTE: for rows reproduction select cell AX2, then click on the header of row 2 - sheet is scrolled to the left and cell A2 is focused.
Column C is selected, cell C1 is focused and the sheet is scrolled to top.
The used has to scroll down to the bottom row again to edit data at the bottom of the sheet.
Column C is selected. The currently visible topmost cell of column C is focused, without scrolling the sheet. Excel works that way
Client-side exported Excel workbooks are exported "uncompressed" (as readable text) and their size is much greater than the original document.
Regression since R2 2019 - 2019.2.514
The exported file is 1015 KB in size. The content of the file may be read as plain text
The exported file is 26 KB or similar size. The content of the file is unreadable binary data
Dear Concerned,
1. Open https://demos.telerik.com/kendo-ui/spreadsheet/index
2. Copy from F3:F15
3. Paste as value (ctrl+shift+v) in H3
4. See it pasted only non-empty cells
Empty cells values should be pasted as well as Excel does.
Dear Concerned,
1. Launch https://demos.telerik.com/kendo-ui/spreadsheet/index
2. Click Background or Text Color icon , select custom color
3. See the popup UI , there is boarder and margin issues, boarder is visible on top,left & bottom side but not on right side
There is an issue with the Date type fields validation in the Spreadsheet.
Here are the reproduction steps:
1. Open https://demos.telerik.com/kendo-ui/spreadsheet/index
2. Import attached xlsx file.
3. There are two date cells (B1 & B2), B2 has a data validation (Date between B1 to ToDay)
4. Try to edit the date using the calendar icon from B2. An empty calendar appears
Note: If I change data validation (remove reference of B1 and put hardcoded date) as below then it works.
Dojo example.
The first row is duplicated.
The first row is not duplicated
If an Excel file that contains Shapes is imported in the Spreadsheet, the imported content cannot be exported back to '.xlsx' file. Saving the imported content to Excel throws an error in the console.
Exporting the Spreadsheet content throws an error in the console:
The Spreadsheet content should be exported to Excel file that doesn't contain the shapes from the imported file
For the time being the Spreadsheet parser is unable to read files which tags are not in the default namespace. Try to open the attached file in this demo project: https://demos.telerik.com/kendo-ui/spreadsheet/index.
You won't be able to load the file. If you open the file in Excel, save the file ("Ctrl+S") and try to load it in the Spreadsheet again, there will be no issues with it. The difference in file's structure before and after being saved in Excel could be seen in the attached screenshot.
The code in red is the structure of the file before saving it and the one in green is after the "save" operation. The difference between the files is that the structure of the one saved in Excel inserts the tags in the default namespace while the original document uses the "x:" namespace.
It will be very useful if we can load files with defined namespaces in their structure.