Hello,
My use case:
On grid dataBound, I am iterating over the table rows to perform some piece of custom logic on the row based off of the backing dataItem. Our production site is using version 2024.1.130, and everything is working great. Our next release we've updated to version 2024.2.514, and when we try adding a record, we get an error; when we try to access the dataItem of the last table-row - the dataItem is undefined. The grid.items() in my case is an array of size 21, and the internal _data array is size 20.
Repro conditions (as far as I can tell):
My workaround:
Simply perform a null check on the dataItem before doing the logic. We are calling DataSource.read in the DataSource.sync success callback anyway, so the grid will reload and the dataBound event will be handled afresh.
I've created the below dojo snippet to demonstrate a simplified version of my use case. I tested with 2024.1.130 and seems to work fine. I noticed the issue starting at version 2024.1.319.
https://dojo.telerik.com/INbSBrSg
A note: No, I don't actually use the internal _data property in my code, just for debugging purposes :)
Thanks!
-Alexa
var datepicker = $("#datepicker").data("kendoDatePicker").reset();
Currently, the Grid provides autoFitColumn and autoFitColumns methods, while the Treelist provides built-in only the autoFitColumn. I would like to have built-in support for the TreeList components, so the behavior to be equivalent to the Grid - example.
dataBound: function(e) {
e.sender.autoFitColumns();
},
I am running into an issue with allowing copy/paste of dates into the filter and cell input fields. Currently, the date fields have validation to support MM/dd/yyyy, and users of the app may be trying to copy dates in that are MM/dd/yy. I would expect Kendo to auto format the date to MM/dd/yyyy after the paste happens, or at least allow support for that, but it doesn't seem to happen.
In the cell, when putting in MM/dd/yy, a validation message appears saying the date is invalid, and there doesn't appear to be a way to override that. In the filter, when putting in MM/dd/yy and submitting the filter, it doesn't stick and completely ignores the date put in.
Steps to reproduce (filter):
Steps to reproduce (cell edit):
Hello!
I was recommended to submit a feature request for this in this feature request. I also commented on a similar forum question.
Dynamically adding/removing tiles via the setOptions method works, however in my case I'm using the containers/tiles to display other widgets (like charts and data grids) in a dashboard. Re-initializing the TileLayout via setOptions forces me to recreate my data widgets, some of which are loading fairly large datasets.
I've been able to work around this using the internal source code for the kendoUI TileLayout, which I dislike doing and am always just one update away from my solution breaking. So far it works - I can add/remove tiles without destroying and re-initializing. I did run into some trouble with resizing and reordering, but I think I've gotten around that.
It seems a common usage for the TileLayout is to display dashboards/remote data. I do think implementing a solution to add/remove tiles without re-initializing would be beneficial for many developers using this widget.
Thank you,
-Alexa
/**
* At the time of this writing, the only kosher way to dynamically add/remove tiles to a kendoUI TileLayout is
* to use the `setOptions` method and pushing/slicing the `containers` array. However, doing this destroys the
* TileLayout and re-initializes it. We would have to re-initialize all the data widgets and submit requests to
* the server all over again. So... I lifted this from the KendoUI TileLayout source code and modified it to
* suit our needs.
* It seems to work, but it just one update away from breaking. I guess I like living on the edge.
*
* @deprecated
* @param options {Object} the kendo.ui.TileLayout `containers` item configuration
* @param idx {Number} the index of the tile to add
* @param kendoTileLayout {kendo.ui.TileLayout} the kendo tile layout instance
*/
const addContainer = (options, idx, kendoTileLayout) => {
const body = $(`<div></div>`).addClass('k-tilelayout-item-body k-card-body');
const headerSettings = options.header;
const id = kendo.guid();
const container = $(`<div></div>`)
.addClass('k-tilelayout-item k-card')
.attr({
id: id,
role: 'listitem',
'aria-keyshortcuts': 'Enter',
});
if (headerSettings && (headerSettings.template || headerSettings.text)) {
const header = $('<div></div>').addClass('k-tilelayout-item-header k-card-header');
const headerContent = headerSettings.text ? `<div class="k-card-title">${headerSettings.text}</div>` : null;
if (kendoTileLayout.options.reorderable) {
header.addClass('k-cursor-move');
}
header.append(headerContent || kendo.template(headerSettings.template)({}));
header.appendTo(container);
}
body.append(kendo.template(options.bodyTemplate)({}));
body.appendTo(container);
container.appendTo(kendoTileLayout.element);
kendoTileLayout._addContainer(container, options, idx, id);
};
/**
* @deprecated
* This also is using KendoUI internal source code. If/when the folks at Telerik decide to implement a different
* solution for dynamically adding/removing tiles, that should be used instead and this should be removed.
*
* @param widgetId {Number} the id of the widget to remove
* @param kendoTileLayout {kendo.ui.TileLayout} the kendo tile layout instance
*/
const removeContainer = (widgetId, kendoTileLayout) => {
const widgetRegex = new RegExp(`${widgetId}`);
const matchedContainer = kendoTileLayout.options.containers.find(container => container.bodyTemplate.match(widgetRegex));
const containerGuid = matchedContainer.id;
const containerItem = kendoTileLayout.itemsMap[containerGuid];
const containerItemIdx = kendoTileLayout.items.indexOf(containerItem);
kendoTileLayout.options.containers.splice(containerItemIdx, 1);
delete kendoTileLayout.itemsMap[containerGuid];
kendoTileLayout.items.splice(containerItemIdx, 1);
$(`#widget-${widgetId}`).closest('.k-tilelayout-item.k-card').remove();
kendoTileLayout._updateContainers();
// I've got a bad feeling about this.
kendoTileLayout.element.off('mousemove'); // after removing a container, the resize handles weren't working.
kendoTileLayout.resizable.destroy();
kendoTileLayout.element.find('.k-resize-handle').remove();
kendoTileLayout.resizeHandle = null;
kendoTileLayout._resizable();
};
In the jquery scrollView component https://docs.telerik.com/kendo-ui/api/javascript/ui/scrollview there is no current way to enableto 'endless' or 'wrap around' option like the react component has
ref: https://www.telerik.com/kendo-react-ui/components/scrollview/endless-scrolling/
Requesting that this feature be added.
For my SPECIFIC my use case (which will probably not work for everyone), I did add a workaround for now
(not fond of it as it relies on the implementation details of the current version)
In our SCSS, I added an override to force the previous/next buttons to always be visible, even after the control hides them
...
&.k-scrollview {
.k-scrollview-prev, .k-scrollview-next {
//Prevent the control from hiding these buttons when it reaches the 'end'
//We will be using some custom logic to force the 'wrap around'
display:flex !important;
...
Then I subscribed click events and did some manual handling on the buttons
//After the page load & scroll view is initialized... //note: $slides is a jquery instance that the scrollView is attached to let scrollView = $slides.data("kendoScrollView"); let $prev = $slides.find('.k-scrollview-prev'); let $next = $slides.find('.k-scrollview-next'); $prev.on("click", function (e) { // NOTE: Here we are looking at an 'internal' variable, this is dependent on the version of Kendo we are using - may need to change // in the future // I figured this out by looking at the implementation in the source // \src\js\kendo.scrollview.js let pageCount = scrollView._content.pageCount; let currentPage = scrollView._content.page; if (pageCount > 1 && currentPage === 0) { e.preventDefault(); e.stopPropagation(); scrollView.scrollTo(pageCount-1); } }); $next.on("click", function (e) { let pageCount = scrollView._content.pageCount; let currentPage = scrollView._content.page; if (pageCount > 1 && currentPage === pageCount - 1) { e.preventDefault(); e.stopPropagation(); scrollView.scrollTo(0); } });
See https://demos.telerik.com/kendo-ui/menu/scrollable
When you hover over the left or right arrow on the menu, the menu scrolls.
Our client *hates* that, and only wants the menu to scroll when you actually click on the left/right arrow.
Request:
Add an option so that we can turn OFF the scrolling on hover on the left/right scroll buttons in the menu.
Support ticket related: https://www.telerik.com/account/support-center/view-ticket/1662811
We are currently utilizing Telerik's Spreadsheet functionality across two different technologies:
- KendoUI for jQuery: This is being used by our FrontEnd users.
- .NET Assembly of Telerik: This is employed for backend processing and interfaces.
Both Spreadsheet implementations allow us to populate data; however, we've observed a discrepancy between the two. Specifically, there is a misalignment in the available functions, where some functions accessible in KendoUI are not available in the .NET Assembly. To address this inconsistency, we request the following enhancements:
1. Unified Function List: We would like an official list of functions that are consistently supported by both the jQuery library and the .NET assembly. Currently, the frontend offers a broader range of functions than the backend. Since our system relies on both for computations, consistency is crucial.
2. Function Usage Detection: We request an event or function in both the JS and .NET implementations that can detect the functions used within a formula. This will allow us to identify discrepancies early on.
3. Backend Validation: An event that triggers when a formula entered on the frontend is valid there but would fail on the backend due to unsupported functions would be invaluable. This will help prevent issues caused by discrepancies between the frontend and backend function implementations.
4. Enhanced Backend Functionality: We also request additional functions or exposed properties on the backend to perform similar checks as described above. This is particularly important for our customizations that allow formulas to be entered directly on the backend, bypassing the spreadsheet UI.
5. Specific Error Handling: On the backend, it would be helpful to introduce a specific error type, distinct from the generic error, that indicates a calculation failure due to an unsupported function in a formula. Currently, the generic error type could indicate multiple issues, making it difficult to diagnose the root cause.
Bug report
TreeList with multi-column headers and row filtering throws an error when user tries to reorder a column.
Reproduction of the problem
Open the Dojo - https://dojo.telerik.com/aFIkOPUp/3
Try to move column "position" left or right
Current behavior
Error is thrown
Uncaught TypeError: Cannot read properties of undefined (reading 'locked')
Expected/desired behavior
Rerdering shall be allowed
Environment
jQuery version: 3.4.1
Kendo UI version: [all]
Browser: [all ]
Dear Kendo UI Team,
I am writing to request the implementation of a mention user feature for the Kendo UI TextArea component. This functionality would significantly enhance the user experience and collaboration capabilities of our .NET application.
Similar to popular social media platforms, the ability to mention users within a text area would allow for efficient communication, tagging, and collaboration among users. This feature could be implemented by enabling users to type an '@' symbol followed by a partial username, which would then trigger a dropdown list of matching user suggestions.
By incorporating this feature, Kendo UI would further solidify its position as a leading UI component library, providing developers with the tools to create more engaging and interactive applications.
Thank you for considering this feature request. We look forward to your response.
Sincerely,
Nasif Ishtiaque Islam
Software Engineer
There is an issue with the .k-sorted class being applied to the last column in the grid when the actual column is not visible. It also is not updating the k-sorted when a sort is applied after the grid was created.
This seems to be an issue in the latest release if the column sorted on is hidden, the last column in the grid gets the class. I also noticed that sorting a column does not apply the k-sorted class to the correct column: https://dojo.telerik.com/@dojolee/eFIbaSUn
Hello,
- I reproduced my problem on this DOJO https://dojo.telerik.com/EpUVIxek , columns are not on the same position with the category because I have 5 column series and 4 of them are 0 in one category.
The observed appearance is due to the data with zero value for each series. Even if the value for a series/bar is zero still there is a placeholder in the Chart for the respective bar. Hiding the data points with 0 value is not supported in the Kendo UI Chart and I am afraid I could not suggest a possible approach for achieving such an appearance.
Can something be implemented so the columns with 0 value to not take place?
Best regards.
I just upgraded from V2021 to V2024. Now, in the grid's filter menu, I have buttons with icons for filter and clear. I don't want the icons. I know I can target them with CSS and do a display: none, but there should be a setting to prevent showing them in the first place. I'm thinking this should be both a global setting for the default and a local setting in the widget to override.
Issue 1:
When I initialize a kendo editor from a div with content, all of the table tools are shown in the editor toolbar (insert row, insert column, etc) on initialization. Once the user clicks in the box they disappear. I prepared a Dojo showing this.
In the Dojo, you will see there are 2 different editors. The first editor uses a function I wrote that worked in version 2022 but doesn't in version 2024 of Kendo. The second editor is just a default initialization using none of my custom code. The purpose of the first one is to show the toolbar on initialization. In both instances of the editor, you will notice that the insert row, insert column, etc are showing at first and then quickly disappear. This only happens the first time the user clicks into the editor. These should not be visible until the user clicks into the editor and selects a table.
I did notice that if I initialize the div empty, then add the content later programmatically (like this: kendoEditor.value("Hello World");), the issue doesn't happen.
Issue 2:
Once you add a table, you can't remove it using backspace or delete. Try this example:
I want to set the mask-character in the TimeDurationPicker.
Display as "08:__" or "__:15" is ugly and I want to display this as "08:00" or "00:15"
Hello,
I would like to request a feature to include normal touch gestures on mobile devices on the PDFViewer, such as zooming in and out. In general, it would be great if the PDFViewer were more mobile friendly.
Thanks.
Currently the dialog action buttons can not hold only icons, the API does not provide means to have a button with only an icon or an icon and text. Considering the aforementioned we should extend the API to allow adding of icons inside the action buttons.
Hi Team,
I would like to share some feedback about the documentation, but I want to make sure it goes to the correct team. Is this the best place to share it?
Thank you,
Michael
**** CREATED BY PROGRESS TECHNICAL SUPPORT ****