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.
Reproduction of the problem
- Follow the steps described in the link here - https://github.com/telerik/kendo-ui-core?tab=readme-ov-file#building-kendo-ui-core
- Create a custom script for validator
npx gulp custom -c validator - Try to load the script and create the components
Current behavior
The validator is not working, error is shown
jQuery.Deferred exception: $(...).kendoNumericTextBox is not a functionExpected/desired behavior
The components should work as expected when custom script is created
Hello Team,
We are currently facing challenges with the Kendo grid, which is a widely used widget or component at o9Solutions. Although we have been using Kendo for a long time, the widget is failing to meet accessibility standards for some components, which are crucial in today's world.
Regarding the Kendo grid, there is an issue where SR is reading the table twice, once for the header and once for the cells. This can cause confusion for assistive technologies like SR.
Consider the cases of horizontal scroll or fixed column cases also.
Having a single <table> is the standard. We can't create multiple tables, which will violate the good coding practices + accessibility standards.
---
I saw some posts regarding this... where it was mentioned we can remove this Scrollable() . But what are the cons of this if we remove this?
--
We want this functionality like a horizontal or vertical scroll or fixed column cases.But it needs to recognize as a single table.
- Are there any specific versions of Kendo UI jQuery that you would recommend for compatibility with strict CSP?
- What potential risks or extensive modifications might be involved in upgrading from our current version to a CSP-compatible version?
Repro steps:
- Open URL: Kendo UI Snippet | Kendo UI Dojo (telerik.com)
- Navigate to the Choose Library combo box and select 'Kendo UI 2022 R2' option.
- Navigate to the Run button and activate it.
- Open Narrator using 'Ctrl + Win + Enter' key.
- Press 'T' key to navigate table in quick navigation mode.
- Navigate the table header controls using up arrow.
- Observe that narrator announce role as link on Filter controls.
Actual Results:
Incorrect role is defined as "link" for the "filter" button, Screen reader announce like "Metric type filter column setting link".
Expected Results:
Correct role should be defined as "button" for the "filter" button. Screen reader should announce like "Metric type filter column setting button".
Hi Guys,
I have just upgraded to v2023.3.1114 only to find out the AngularJS directives have been completely removed from this release, causing a lot of wasted time & effort triaging the errors and then rolling things back to a previous working revision.
Back in a February 2018 blog post, you stated you were dropping support for AngularJS in all new components which was understandable but what I didn't expect was it's complete removal, especially in a SP, without any further communication.
The v2023.3.1114 release notes do not even list this as a breaking change, so are you expecting your customers to be clairvoyant now or is this just another example of how poor Telerik's customer service has become in the past few years?
Regards
Alan
I have a tab control, and a number of the related views contain grids.
If a grid is created in a tab view that is not visible, then the grid pager renders as if it was on a tiny mobile screen. The only way you can make it render the pager correcly is to manually resize the browser window after the grid has become visible.
I have a simple demonstration here: https://dojo.telerik.com/eCuQAqEm
The behavior is the same in both Chrome and Firefox.
<!DOCTYPE html>
<html>
<head>
<base href="https://demos.telerik.com/kendo-ui/tabstrip/index">
<style>html { font-size: 14px; font-family: Arial, Helvetica, sans-serif; }</style>
<title></title>
<link href="https://kendo.cdn.telerik.com/themes/6.7.0/default/default-main.css" rel="stylesheet" />
<script src="https://kendo.cdn.telerik.com/2023.2.829/js/jquery.min.js"></script>
<script src="https://kendo.cdn.telerik.com/2023.2.829/js/kendo.all.min.js"></script>
</head>
<body>
<div id="example">
<div class="demo-section">
<div id="tabstrip">
<ul>
<li class="k-active">
Visible Grid
</li>
<li>
Hidden Grid
</li>
</ul>
<div>
<div id="visibleGrid"></div>
</div>
<div>
<div id="hiddenGrid"></div>
</div>
</div>
</div>
<script>
const data = [];
for (let i = 0; i < 100; ++i) {
data.push({
columnOne : `Item ${i} Column One`,
columnTwo : `Item ${i} Column Two`
});
}
const gridOptions = {
dataSource: data,
pageable: {
refresh: true,
pageSize: 10,
pageSizes: [10, 20, 30]
},
};
$(document).ready(function() {
$("#tabstrip").kendoTabStrip();
$("#visibleGrid").kendoGrid(gridOptions);
$("#hiddenGrid").kendoGrid(gridOptions);
});
</script>
</div>
</body>
</html>
Hi Team, we're using kendo heavily on our platform. But still there're many gaps in kendo accessibility. I'm working as a Accessibility advocate and i believe every individual can access the widgets irrespective of their barriers. One of the issue is:
Keyboard Support is missing in the input fields buttons like:
1. Clear Button
2. Dropdown "arrow" Button
3. Date and Time Button
Current Behavior:
Focus is going to input field and you can write inside the combobox or textbox or multiselect but you can't interact with other icon buttons like dropdown , date & time, clear "x" button using tab key.
Expected Behavior: As per accessibility , every interactive elements needs to be keyboard focusable using tab key irrespective of shortcut.
I've created a feature request long ago and suggested solution for this: please check in the feature, it's declined by the team:
Date time picker Keyboard Support is missing for date and time button because of (tabindex=-1)
Hi,
you have an open DatePicker on a mobile device and want to scroll up or down.
If you press and hold the screen inside the popup you can scroll but when you release the screen the date is selected and the DatePicker closes.
Shouldn't the DatePicker stay open because the user just wanted to scroll the page?
If you do the same with a DateRangePicker it's working. The date is selected but stay's open.
Thank you!
Hi,
When "filter" option is set for dropdown tree widget, "checkChildren" option doesn't take effect even if it is set to true.
Please, check example:
https://dojo.telerik.com/iMaVehuS/6
Thank you.
Hi Support Team,
I try to apply VLOOKUP function in demo page.
VLOOKUP Function: =VLOOKUP(B8, 'Food Order #1'!B3:F11, 5, true) , the result showing in spreadsheet is $13.19, but when export to PDF the result show in PDF change to $52.16.
Can you please check on this issue.
Thank you
Regards
Daniel
Describe the bug
Kendo ComboBox and DropDownList controls are conflicting with kendo PanelBar.
If ComboBox or DropDownList control is included inside a kendo PanelBar, the the dropdown elements of both controls are detached from the combobox or dropdownlist inputs respectively.
To reproduce
In order to reproduce the behaviour:
- Create a kendo PanelBar with one item
- In the previously created panel's bar item create a list
- Add input value in one of the list items
- Add ComboBox or DropDownList kendo control to the input
- Both controls will have detached the dropdown elements
- You can run the piece of code in dojo to reproduce the issue (https://dojo.telerik.com/OZoXiPEy)
Expected behavior
ComboBox or DropDownList controls should work correctly and the dropdown elements of controls should not be detached.
I have some client events for creating/updating events.
They are currently the same and call the same method:
Due to JSON serialization, I end up with dates being serialized as ticks when sent to the client. This function converts these ticks to a proper JavaScript Date() object. The code works perfectly fine.
We run into an error on random occasions. This happens maybe once a day per user. It is not repeatable but it was fixable. This code is from the Kendo.all.js file. The highlighted lines were added:
99% of the time things work fine. But sometimes this convertData() method is called before the client methods are called. Perhaps a threading or AJAX or promise issue? Perhaps there is one scenario where the client method is not being called? The real bug here is that convertData() can sometimes get called before the client’s event where I would have corrected by dates. This is another case where it is tough to upgrade Kendo versions because I need to port this as minified JavaScript to the custom downloaded minified file.
Here is the text from the browser’s F12 window when we hit this error (If I have not applied the fix above):
kendo?v=Brdc2jM0hzOFDq3Kj04CDAYP5xcGXPDm3x-vN4slHho1:1 Uncaught TypeError: f.start.getTimezoneOffset is not a function
at ai (kendo?v=Brdc2jM0hzOFDq3Kj04CDAYP5xcGXPDm3x-vN4slHho1:1:1182628)
at init.data (kendo?v=Brdc2jM0hzOFDq3Kj04CDAYP5xcGXPDm3x-vN4slHho1:1:1182352)
at init._readData (kendo?v=Brdc2jM0hzOFDq3Kj04CDAYP5xcGXPDm3x-vN4slHho1:1:96753)
at init._push (kendo?v=Brdc2jM0hzOFDq3Kj04CDAYP5xcGXPDm3x-vN4slHho1:1:90345)
at init._pushUpdate (kendo?v=Brdc2jM0hzOFDq3Kj04CDAYP5xcGXPDm3x-vN4slHho1:1:90237)
at init.e (jquery?v=9zl6bqYAmbr9FSUZX0T1VSNbWQ5Gc01X9-RaVvSk-7A1:1:95021)
at init.a (signalr?v=4OffKgJP3BKl-a0HMCu8SoFYj-iqmWy-1sbyLwYhtvk1:1:36810)
at init.dispatch (jquery?v=9zl6bqYAmbr9FSUZX0T1VSNbWQ5Gc01X9-RaVvSk-7A1:1:55579)
at y.handle (jquery?v=9zl6bqYAmbr9FSUZX0T1VSNbWQ5Gc01X9-RaVvSk-7A1:1:53581)
at Object.trigger (jquery?v=9zl6bqYAmbr9FSUZX0T1VSNbWQ5Gc01X9-RaVvSk-7A1:1:78599)
In my application, when a user changes their view date on the scheduler, there are two other schedulers on the other two tabs of the tab strip that are not visible. The dates here get changed too. This happens in a navigate event. They end up in a broken state from this. It seems the issue is that they are not visible so rendering is not happening. I found a hacky way to work around this. I am adding a newDate property and a needRefresh property to the scheduler. When a tab is activated, the scheduler in that tab is checked. If it needs a refresh, it is refreshed. If it has a new date, that is also set.
The schedulers are sitting inside a tab strip control. When the page loads, some computations are done by Kendo for setting up column widths. I feel there is a scrollbar issue somewhere. As it is a larger screenshot, please look at the attached Scrollbar size computation issue.png file. Start with the “All day” events. Notice the first event on Monday crosses the line into Tuesday just a little bit. This is highlighted and indicated with a “2” on it. Now look at the events for the week – numbers 3, 4, and 5. The events span into the next column a little more each time. They WOULD be correct if there was no scrollbar on the right! Now look at the events below with a time. “1” has the correct left offset from Monday’s left side. As you go to 2, 3, 4, and 5, this offset grows. It’s the same issue.
Now look down at “6”. Notice the scheduler has no footer and is drawing far too low.
The problem is that the tabstrip content is allowing scrolling. I can see this in the F12 window. Notice the scheduler does not have the scrollbar:
But the tab strip content DOES have a scrollbar:
Please note that I am specifically blocking the tab strip from scrolling in my code. The scheduler should handle the scroll.
So, I added the following CSS which fixes this issue for me:
See the Scrollbar size computation fixed.png file for the end result. The scheduler is scrolling now instead of the tab strip.
From the kendo.common-bootstrap.css file:
This cuts off the dates which have ample room to be displayed (this is my app):
I overrode this to remove the max-width:
In the scheduler component, create a new event. Select monthly for the repeat. If you are using the Bootstrap theme the day will be cut off. The problem lies in the kendo.common-bootstrap.css file.
Overriding to 10em works. The same issue exists on the demo site today which I assume is running the current version (https://demos.telerik.com/kendo-ui/scheduler/index?autoRun=true&theme=bootstrap-main):
Hello, I have been using your service for almost a year and I noticed that your search engine could be significantly improved.
For example, I asked the following question in the forum on 18/10/2022:
"org chart editable.fields => set editable: false doesn't work"
And indeed I received an adequate response,
Then I tried to type this question into the browser but I couldn't find it,
Unlike if I were to ask such a question in Stack Over Flow then I would surely find my question through Google's smart search engine.
You have a huge database of questions and answers but it is a bit difficult to find what you want.
If a user can find questions asked by other users by simply typing in the browser, you will be able to provide a much greater response to customers.
Hope I explained myself clearly.
Hello kendoUI Team,
I am 98% sure the following is a bug: https://dojo.telerik.com/UZuKImUs/2
In this Dojo link, the AM/PM designators are logged to the console for the cultures en-US and de-DE. They appear to be empty for de-DE. Consequently, a custom format string "yyyy.MM.dd hh:mm:ss tt" will result in a formatted Date without the AM/PM designator at the end for the de-DE culture, instead ending with a trailing whitespace (i.e. the whitespace between "ss" and "tt" in the format string).
The JS console output for this Dojo code is:
AM designator(s) for en-US culture: AM, am, AM
PM designator(s) for en-US culture: PM, pm, PM
Format "yyyy.MM.dd hh:mm:ss tt" for en-US culture: "2011.01.01 12:27:36 PM"
AM designator(s) for de-DE culture:
PM designator(s) for de-DE culture:
Format "yyyy.MM.dd hh:mm:ss tt" for de-DE culture: "2011.01.01 12:27:36 "
Contrast this with the following equivalent .NET snippet:
using System.Globalization;
var testDate = new DateTime(2011, 1, 1, 12, 27, 36, 952);
var dateTimeTestFormat = "yyyy.MM.dd hh:mm:ss tt";
Thread.CurrentThread.CurrentCulture = new CultureInfo("en-US");
Console.WriteLine($"AM designator(s) for en-US culture: {Thread.CurrentThread.CurrentCulture.DateTimeFormat.AMDesignator}");
Console.WriteLine($"PM designator(s) for en-US culture: {Thread.CurrentThread.CurrentCulture.DateTimeFormat.AMDesignator}");
Console.WriteLine($"Format \"{dateTimeTestFormat}\" for en-US culture: {testDate.ToString(dateTimeTestFormat)}");
Thread.CurrentThread.CurrentCulture = new CultureInfo("de-DE");
Console.WriteLine($"AM designator(s) for de-DE culture: {Thread.CurrentThread.CurrentCulture.DateTimeFormat.AMDesignator}");
Console.WriteLine($"PM designator(s) for de-DE culture: {Thread.CurrentThread.CurrentCulture.DateTimeFormat.AMDesignator}");
Console.WriteLine($"Format \"{dateTimeTestFormat}\" for de-DE culture: {testDate.ToString(dateTimeTestFormat)}");The output of this C# code is:
AM designator(s) for en-US culture: AM
PM designator(s) for en-US culture: AM
Format "yyyy.MM.dd hh:mm:ss tt" for en-US culture: 2011.01.01 12:27:36 PM
AM designator(s) for de-DE culture: AM
PM designator(s) for de-DE culture: AM
Format "yyyy.MM.dd hh:mm:ss tt" for de-DE culture: 2011.01.01 12:27:36 PM
While I am aware that kendo.culture cannot be a carbon copy of .NET's CultureInfo, I'm pretty sure that the missing AM/PM designators for the "de-DE" culture (possibly for others as well!) are an oversight in this particular case.
There are several problems when extending a widget .
In this example we have extended the DropDownTree.
- Some properties like fillMode, no matter if we set in in the options or in the extended widget it self (kendoDemoDropDownTree)
sets the value but never actually applies. Also the dataSource must be in the following format
selectedProductId: [{ id: "a" }, { id: "c" }],and not
selectedProductId: ["b", "c"]So some properties are supported and other that have been added later not.
I present you the source code (https://dojo.telerik.com/ewewERiD)
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Untitled</title>
<script src="https://code.jquery.com/jquery-1.12.3.min.js"></script>
<script src="https://kendo.cdn.telerik.com/2022.2.510/js/angular.min.js"></script>
<script src="https://kendo.cdn.telerik.com/2022.2.510/js/jszip.min.js"></script>
<script src="https://kendo.cdn.telerik.com/2022.2.510/js/kendo.all.min.js"></script>
<link rel="stylesheet" href="https://kendo.cdn.telerik.com/2022.2.510/styles/kendo.default-ocean-blue.min.css">
</head>
<body>
<input id="dropdowntreeExt" data-bind="value: selectedProductId">
<script>
(function ($) {
var kendo = window.kendo,
ui = kendo.ui,
DropDownTree = ui.DropDownTree;
var DemoDropDownTree = DropDownTree.extend({
init: function (element, options) {
DropDownTree.fn.init.call(this, element, options);
$(element).parent().addClass("k-picker-solid k-picker k-rounded");
},
options: {
name: "DemoDropDownTree",
checkboxes: true,
fillMode: "flat"
}
});
ui.plugin(DemoDropDownTree);
})(jQuery);
var viewModel = kendo.observable({
selectedProductId: [{ id: "a" }, { id: "c" }],
//selectedProductId: ["b", "c"],
products: [
{ id: "a", name: "Coffee" },
{ id: "b", name: "Tea" },
{ id: "c", name: "Juice" }
]
});
kendo.bind($("#dropdowntreeExt"), viewModel);
//kendoDemoDropDownTree
//kendoDropDownTree
$("#dropdowntreeExt").kendoDemoDropDownTree({
valuePrimitive: true,
dataTextField: "name",
dataValueField: "id",
//checkboxes: true,
dataSource: viewModel.products//,
//fillMode: "flat"
});
alert($("#dropdowntreeExt").data("kendoDemoDropDownTree").options['fillMode']);
</script>
</body>
</html>(!) This also applies in the latest versions as well (2022R2 and 2022R3).
2. if you place the properties in kendoDropDownTree, everything works well and the datasource also accepts the format selectedProductId: ["b", "c"]
3. Many options, like autoWidth property, don't apply in extended widgets (i.e. MultiSelect, DropDownList, DropDownTree etc).
4, In DropDownTree for the extended widget, valuePrimitive: true is not applicable. Instead of returning an array of the selected keys, it returns an array of the entire item.