Context: There is an item that illustrates the issue here: https://www.telerik.com/forums/kendo-datepicker-value-not-populated-after-refresh-firefox-only
In Firefox, when using the asp-for tag helper to bind a c# DateTime field to an input element, then calling kendoDatePicker() on that element, the control fails to populate on a soft-refresh (F5). Upon reloading using F5 in Firefox, the input's type is set to datetime-local, and the input 's control variation is changed to the default date picker. Then, the Kendo UI DatePicker is initialized with a blank input which normally has a type of text.
Example project and video of issue are attached.
This is the pertinent code (also happens in latest version of Kendo as well):
public class IndexViewModel
{
public DateTime DateAsDateTime { get; set; }
}
public IActionResult Index()
{
return View(new IndexViewModel { DateAsDateTime = DateTime.Today });
}
@model IndexViewModel
<input id="dtDate" asp-for="@Model.DateAsDateTime">
<script type="text/javascript">
$(document).ready(function () {
$("#dtDate").kendoDatePicker();
});
</script>
The DropDownTree allows us to configure its checkChildren and filter options. Both options are working correctly, when used separately.
When the two options are defined for the DropDownTree, the checkChildren options don't select the child elements of a given node that is checked.
Only the "Furniture" checkbox is being checked
The "Furniture" and all of its child nodes should be selected when clicking on the "Furniture" checkbox.
Here is a Dojo example in which the checkChildren configuration is working as expected.
In the latest version of Kendo UI, various input controls like the NumericTextBox or the ColorPicker now consist of an input field and a button control (used for increasing/decreasing the value or opening the dropdown).
The border-radius for those widgets can be controlled by setting the "rounded" option. At the same time, when using SASS themes, a button's default border-radius might be set using the $kendo-button-border-radius variable. The buttons inside e.g. a NumericTextBox do not override the theme's border-radius which leads to an outcome like this:
Widgets that use Buttons internally (and therefore offer no way of overriding the button's border-radius by setting its "rounded" option manually) should override the default styles.
Unfortunately, I could not reproduce the behavior in a DOJO, because I cannot transpile SASS themes there.
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.
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?
npx gulp custom -c validator
The validator is not working, error is shown
jQuery.Deferred exception: $(...).kendoNumericTextBox is not a function
The components should work as expected when custom script is created
The "Classic" SASS theme for Kendo UI (v. 5.4.0) provides the $enable-transitions variable. I expected it to behave consistent with other similar variables like $enable-rounded which means that when it is set to false, no transistion properties would be set.
However, the following elements always have a transition property set, no matter what the value of $enable-transitions is:
Is this a bug or did I understand the meaning of $enable-transitions wrong?
Environment (OS, Application, Versions):
OS Version: 22H2 (OS Build 25352.1)
Edge Dev: Version 121.0.2277.112 (Official build) (64-bit)
Third Party Name: Kendo
Repro Steps:
1. Open https://codepen.io/oneID/pen/LYaGREP and turn on NVDA.
2. Navigate to 'Populate' grid and activate it using enter key.
3. Navigate to Expand button present under domain in Export to excel table.
4. Observe if the screen reader is announcing correct role and name for the expand button or not.
Actual Results:
Accessible name for the 'expand' button is not correct, Expand button is defined as link.
Expected Results:
Accessible name of 'expand' button should be sufficient for screen reader user. Accessible name should contain value available in domain as well.
Role should be defined as 'Button' as its behaving as button.
Bug report
ExpansionPanel control is not collapsing/expanding when set up collapseIconClass
Regression since R1 SP1 2023
Reproduction of the problem
Dojo: https://dojo.telerik.com/AqOrUKib
Expected/desired behavior
The user shall be able to set expand and collapse icons
Environment
Kendo UI version: 2023.1.314 or newer
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.
Files are missing when trying to generate a script file for CircularProgressBar only through the Custom Download Tool.
There are missing files in the exported custom file.
All necessary files should be included in the custom script file.
Bug Title: Filter controls are not accessible via keyboard under 'Security Groups and Service Accounts' screen.
Severity: Sev1 (Critical)
Test Environment: OS: Windows 11 22H2
OS Build: 23620.1000
Repro steps:
1.Open https://codepen.io/oneID/pen/LYaGREP
2.Activate populate grid.
3.Try navigating to Column filter controls using keyboard.
4.Observe whether filter controls are accessible via keyboard under 'Security Groups and Service Accounts' screen or not.
Actual Result:
Keyboard focus does not remain on same control after pressing 'ESC' key to close the opened ‘Filter’ popup present under 'Security Group' screen.
Expected Result:
Keyboard focus should remain on same control after pressing 'ESC' key to close the opened ‘Filter’ popup present under 'Security Group' screen.
Bug Title: Columns are not programmatically associated with their table headers.
Severity: Sev2 (High)
Test Environment:
OS Version: 22H2 (OS Build 25352.1)
URL: https://ppe.oneidentity.core.azure-test.net/
Edge Dev: Version 114.0.1807.6 (Official build) dev (64-bit)
Screen Reader: Narrator
Repro steps:
1.Open kendoSample (codepen.io)
2.Navigate through tables.
Actual Result:
Table header and their data are in different tables. Columns are not associated programmatically with their headers.
Expected Result:
Columns should be associated programmatically with their headers.
In a very special case it is impossible to select a value from the ComboBox. It only occurs on iPads.
if ComboBox filter is set, virtualization is on and the datasource is set programmatically after initialization. A data item cannot be selected from the list if it is filtered before hand and the item is located at the second page inside the popup.
Steps to reproduce:
Used Dojo Snippet:
<!DOCTYPE html>The kendo.culture.nb-NO.min.js file contains some unwanted characters: "Â".
See Ticket ID: 1486493 for more details.
The unminified file looks correctly: https://github.com/telerik/kendo-ui-core/blob/master/src/cultures/kendo.culture.nb-NO.js