Hello everyone, I'm Darshan Hiranandani, currently grappling with CORS (Cross-Origin Resource Sharing) issues in my web application and could use some assistance. Has anyone encountered similar challenges and successfully resolved them? If so, could you please share any tips, tricks, or troubleshooting steps you used to overcome CORS issues in your projects? Any advice would be greatly appreciated. Thank you for your help!"
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.
Currently, the kendo.culture() method accepts only a string argument which is used for mapping an included culture file.
However, it would be beneficial if additional arguments could be passed to the method as well which may override some of the culture file's existing options. For example:
kendo.culture("bg-BG", {
numberFormat: {...},
calendars: {...}
})
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>
The children of a node (if the children are all leaf nodes) vertically stack when parent is expanded. Can you add a setting that forces horizontal sibling orientation for leaf nodes.
Current:
Desired:
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)
Hi team, please find the accessibility issue:
Component: https://demos.telerik.com/kendo-ui/datetimepicker/keyboard-navigation
Issue Name:
Missing keyboard support for image buttons
Actual Result
Keyboard support is missing for "Open the time view" and "Open the date view" image buttons. This made it difficult for keyboard-only and screen reader users to access the functionality associated with the image buttons.
Steps to Reproduce
1. Navigate to the mentioned image buttons in the modal dialog.
2. Observe that the image buttons do not receive the keyboard focus.
Expected Results
The image buttons must be keyboard accessible.
Recommendation
Ensure that all the page functionality is available for all users irrespective of the device being used.
Apply the following changes:
• Remove the tabindex="-1" attribute from the source code of the image buttons.
• Initially set the aria-expanded attribute to "false" for the image button. Ensure that the value of the aria-expanded attribute changes on user interaction via scripting.
Existing:
<button unselectable="on" tabindex="-1" class="k-select k-input-button k-button k-button-md k-button-solid k-button-solid-base k-icon-button" aria-label="Open the time view" type="button">
<span class="k-icon k-i-clock k-button-icon"></span>
</button>
Recommended
<button unselectable="on" class="k-select k-input-button k-button k-button-md k-button-solid k-button-solid-base k-icon-button" aria-label="Open the time view" type="button" aria-expanded="false">
<span class="k-icon k-i-clock k-button-icon"></span>
</button>
Also, the shortcut is there to open a date and time picker but relying on the shortcuts only to open it would not be feasible,
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.
we are extensively using the Kendo Jquery Grid for our datasets. The pager can be positioned at either the top of the grid or the bottom of the Grid using the configuratioon within the Grid Pager definition. I find having two pagers better when the display grid take up more than a view port, then you can sometimes be closerto the top of the grid, sometimes closer to the bottom. If the Page is just at the top or the bottom then some cases you have to scroll throrough the entire grid to get to the pager. So when it present at both, you can have eaiser access to the Pager.
So I am requesting that the position configuration in the grid is Top, bottom, Both.
Mark D
Hi Team,
I would like to request the functionality to be able to define a character set for the Telerik.Web.Captcha. Additionally, I'd like to request a way to exclude certain characters like numbers.
Thank you!
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!