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
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.
Select event not fired on clicking over already selected ComboBox/MultiColumnComboBox item. According to the event description, it should be "Fired when an item from the popup is selected by the user either with mouse/tap or with keyboard navigation". It is fired when pressing Down arrow again when the last item is selected, but not fired if the last item is clicked.
Regression since 2018.3.1017 - Dojo introduced with the fix for Unexpected ComboBox value selection, instead of text, when an item is selected with Enter
Select event is NOT fired.
If we expand the widget and press Down arrow, select event is fired once again for Item 3.
Select event is fired as with version 2018.3.911 - Dojo.
Repro steps:
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".
Title: Keyboard focus loss is observed after closing the filter pop-up by 'Esc' key.
Description: Keyboard users will be impacted here , as focus is getting lost after closing the filter pop-up.
Environment (OS, Application):
Test Environment:
OS version (OS Build 22000.856)
Microsoft Edge : Version 105.0.1343.25 (Official build) (64-bit)
URL: https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/filterable
Repro Steps:
1. Open given URL in Edge Dev.
2. "Kendo UI for jQuery" page will be open.
3. Navigate to "Preview" button present under filterable.
4. Navigate to the filter controls present on the table.
5. Activate the filter control using mouse and navigate over the pop-up.
6. Press 'Escape' key on the flyout and Verify that Keyboard focus loss is observed after closing the filter pop-up by 'Esc' key or not
Actual Result:
Keyboard focus loss is observed after closing the filter pop-up by 'Esc' key.
On pressing Tab key further focus start moving from "Related Properties" link.
Expected Result:
Keyboard focus loss should not be observed after performing any action on the page and should restore on the control which has been activated, here after pressing 'Esc' key, focus should restore on 'Filter' button only.
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>
Description:
If screen reader is not announcing the role as button for Grid pagination controls then users will confuse and not able to utilize the control properly.
Environment (OS, Application):
Test Environment:
OS version (OS Build 22000.856)
Microsoft Edge : Version 105.0.1343.25 (Official build) (64-bit)
URL: https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/pageable
AT (include version number):
Narrator
Repro Steps:
1. Open given URL in Microsoft Edge .
2. "pageable - API Reference - Kendo UI Grid | Kendo UI for jQuery" page will open.
3. Turn on Narrator.
4. Navigate to the Grid pagination buttons using keyboard.
5. Verify that screen reader is announcing role as button or not.
Actual Results:
The pagination buttons at the bottom of grids have their role defined as link.
Expected Results:
The pagination buttons at the bottom of grids should have their role defined as a button, not link.
Additional notes:
This issue is present on any page grid pagination is used, so should address it globally
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)
Test Environment:
OS: Windows 11 Version 22H2(OS build 22621.1992)
Browser: Edge browser version 115.0.1902
Screen Reader: Narrator.
Repro Steps:
Actual Result:
Incorrect role defined as "link" for the "Metric type filter column setting" button.
Expected Result:
Correct role defined as "link" for the "Metric type filter column setting" button.
Missing Anti-CRSF tokens trigger security alerts when testing for security compliance with OWASP ZAP.
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:
Expected behavior
ComboBox or DropDownList controls should work correctly and the dropdown elements of controls should not be detached.
This is observed also in online demos:
Steps:
Hi team,
Found an issue with column filterable property on IE 11 and last kendo UI for jQuery release.
Please have a look at this dojo with IE11: https://dojo.telerik.com/UfIZePaZ
Using property "filterable: { multi: true}" on first column leads to the grid not being built with console error.
Regression bug as it works with previous kendo release.
Regards,
Laurent.
Bug report
When the Kendo UI Grid is paged and the Search panel input is focused, the page is automatically switched to the first one.
Reproduction of the problem
1. Navigate to the live demo:
https://demos.telerik.com/kendo-ui/grid/search-panel
2. Change page to 2 (for instance).
3. Focus the Search panel input.
4. The page is changed to the first one.
Expected/desired behavior
When the search panel is empty and only focused, the page should remain the same.
Environment
* **Kendo UI version:** 2019.3.1023
* **jQuery version:** 1.12.4
* **Browser:** [ IE 11.768.17763.0]