If the ColorPicker tools in the Editor are configured to render a gradient, you cannot type in the HEX/RGB inputs.
The inputs are not selectable and you cannot type in them.
The inputs should be selectable so that you can type in them.
The Editor doesn't allow multiple separators through the tools configuration.
Only the first separator is rendered.
All the separators should be rendered
There is an option to freeze the left most column of the Kendo Grid by setting the lockable property. But this is limited to the Left Hand Side columns only and there are no ways suggested to freeze the Right Most columns.
I would like be able to have a vertical scrollbar on a kendo grid without enabling horizontal scrolling.
Currently when the scrollable feature is set to true, scrolling is enabled for both horizontal and vertical.
I would like to see something like:
scrollable:{ vertical : true, horizontal: false }
Can that be done?
Thank you!
Inline Editor does not close if you drag it to another position. Additionally, while dragging, occasionally the Editor will disappear, or it will have a padding from the cursor.
Regression introduced with 2023.2.606
Video - http://somup.com/cZeOQ5CYa8
The inline Editor remains open when it loses focus
Thе inline Editor should close when it loses focus
Currently, there is no way to reuse a single method of a model and execute different logic based on additional data related to the specific element.
Before the CSP improvements in R1 2023, an unsupported workaround was configuring the method along with the arguments that were evaluated and accessible from the method itself.
Example of the unsupported approach:
<div id="test">
<p data-bind="text: spanLabel('test')" ></p>
<p data-bind="text: spanLabel('another test')"></p>
</div>
<script>
var viewModel = kendo.observable({
spanLabel: function(args){
return "spanLabel executed, args: "+ args
},
});
kendo.bind($("#test"), viewModel);
</script>
Improvement suggestion
Allow the model methods to have access to the reference element. That would enable the internal method logic to get additional data based on the element and achieve the same functionality as the unsupported workaround approach.
Example of the desired functionality:
<div id="test">
<p data-bind="text: spanLabel" data-span-label="test"></p>
<p data-bind="text: spanLabel" data-span-label="another test"></p>
</div>
<script>
var viewModel = kendo.observable({
spanLabel: function(args) {
let element = args.referenceElement;
let spanLabelArgs = element.attr("data-span-label")
return "spanLabel executed, args: " + spanLabelArgs
},
});
kendo.bind($("#test"), viewModel);
</script>
Describe the bug
When there is an event that lasts multiple days, but is not an all-day event the title and the up arrow overlap, thus it makes the reading of the title harder.
To reproduce
Open the Dojo - https://dojo.telerik.com/@NeliK/IruYeGEc
Expected behavior
The arrow and the title should be rendered with some margin
Workaround
.k-event-template{
margin-top: 8px !important;
}
Affected package (please remove the unneeded items)
Affected suites (please remove the unneeded items)
Affected browsers (please remove the unneeded items)
Hi,
When I double click a cell and enter into editing mode, scrolling up or down will make the editor div out-of-place.
It should follow the target cell instead.
This can be easily reproduced here: https://demos.telerik.com/kendo-ui/spreadsheet/index
It seems Kendo UI for Angular/React also have the same issue.
Steps:
Expected: kendoConsole logs the dataItem info in the top message
Actual: dataItem() doesn't find the model even though it exists in the Grid dataSource
In the Grid source code in the refresh function, _data is set to dataSource.view() if partialUpdate is true. For a grouped dataSource, view() will return the parents. This breaks the dataItem function since it relies on the flat array for retrieval.
It looks like this issue was introduced in version 2024.1.319 as it doesn't seem to affect 2024.1.130.
Set an indicator same way that grid already does but now in sheet cells when a record is 'dirty'.
In cases when we have loadOnDemand set to true and we want to populate the value of the DropDownTree initially we need a way to check if this value is part of the available options. One possible solution is adding a valueMapper function similar to the one use in virtualization scenarios.
Currently you can clone the Pager to make it appear both on Top/Bottom. This should be configurable so that you can have in on top of the grid or the bottom of grid or both
Please add the following things in Kendo UI validators for compare, password length check, password complexity check, RangeValidator, ValidationSummary
The PivotConfigurator is very static. It would be nice to change the layout. For example some options: - Hide / visibility of all four elements (Row, Column, Measure, Fieldlist) - Position of all four elements (Row, Column, Measure, Fieldlist)
Having a character counter for textbox & textareas gives users nice little heads up as they start typing to summarize the text for a fixed length. Not sure about internet applications but its becoming more & more a requirement in business applications. Please give it a thought.
SVG Example: <svg> <defs> <pattern id="Occupied" width="4" height="10" patternUnits="userSpaceOnUse" patternTransform="rotate(45 50 50)"> <line stroke="#ffb29d" stroke-width="2" y2="10"/> </pattern> </defs> <rect x="5" y="5" width="40" height="100" fill="url(#Occupied)" stroke="#ff7094" stroke-width="1" /> </svg>
Dojo: https://dojo.telerik.com/@jay/AhUYayEx
1. Hover over a color - tooltip shows up;
2. Hover over the tooltip;
3. Move the cursor back to the same target;
4. Move the cursor to a different color or any mouseout;
Actual: Tooltip is not closed
Expected: Tooltip to be closed (same as when not performing step 2)
kendo.all.min.js is reporting this in Chrome.
A page or script is accessing at least one of navigator.userAgent
, navigator.appVersion
, and navigator.platform
. In a future version of Chrome, the amount of information available in the User Agent string will be reduced.
To fix this issue, replace the usage of navigator.userAgent
, navigator.appVersion
, and navigator.platform
with feature detection, progressive enhancement, or migrate to navigator.userAgentData
.
Note that for performance reasons, only the first access to one of the properties is shown.
https://blog.chromium.org/2021/05/update-on-user-agent-string-reduction.html
When will this be resolved?