Hello Telerik Team, I'm implementing HeaderContext filtering with checkbox lists on a RadGrid in a legacy ASP.NET WebForms application. Current Setup: - FilterType="HeaderContext" - FilterCheckListEnableLoadOnDemand="true" - OnFilterCheckListItemsRequested event populates checkboxes from session data Issue: Users experience 500-2000ms delay when opening filter menus (AJAX callback to server). In our production environment with slow network and high concurrent users, this creates poor user experience. Questions: 1. Is there a way to pre-populate checkbox lists during grid initialization (avoiding AJAX callback)? 2. Can we use OnItemCreated to populate checkbox lists with FilterCheckListEnableLoadOnDemand="false"? If so, what's the correct approach? 3. Is there a client-side caching mechanism for checkbox list items? 4. What's the recommended pattern for large datasets (1000+ rows) with multiple filterable columns? Environment: - Telerik.Web.UI version:v4.0.30319- .NET Framework: 4.8 - Browser: Chrome, IE11 - Grid has ~10 columns with 5 using checkbox filters Any guidance on performance optimization would be greatly appreciated! Thank you, Anurag pandey
Please implement WAI-ARIA support in RadSearchBox with and without a Search Context. It needs the same type of logic added as the AutoComplete and ComboBox control so that JAWS can speak and navigate the list items properly. It looks like there was a little started because it renders an ARIA live region for status, but never writes to it from what I can tell. I know this document lists the current controls that support ARIA - http://docs.telerik.com/devtools/aspnet-ajax/controls/wai-aria-support-and-screen-readers Thanks, Mike
Hi Please add rtl support to RadDropDownTree. Thanks
Add an option to support the automatic repetition of the video.
The control should provide support for the JAWS screen readers, which will enable it for use by visually impaired users. More details are available in the following forum thread - https://www.telerik.com/forums/how-is-listbox-usable-for-screen-readers
There are some areas within the RADEditor that do not support localization: 1. Alerts for Accept All and Reject All track changes. 2. The Comments user interface. 3. Certain strings in the Undo menu. See attached.
Provide keyboard support for the MediaPlayer.
Some of the occurring problems are:
Keyboard navigation is required for 508 accessibility support. Generally the space bar is used to start/stop video and tabs are used to access the playbar features like expand, vol and CC
Hi,
We need to add an aria-label attribute to the RadEditor toolbar link buttons to match the title attribute text. I have been successful using JQuery on other controls to improve accessibility, but this one is not working. It appears because the link button is not rendered since is a pseudo element using the ::before. I have been unable to inject the attribute on page load.
The issue is for screen readers the editor buttons are not announced when using the arrow key navigation which is called virtual mode. The buttons do announce when using the tab key which is called forms mode.
If this can be a bug fix it would benefit everyone, otherwise, if you have a code suggestions that is helpful. Image attached.
Thank you.
WAVE tool indicates errors in RadTreeView when CheckBoxes are enabled for the Control:
Noticed that when using a template to custom define the pager look, the pager gets rendered in a TD and not a TH as expected since the pager is in a THEAD. Could the header pager only be modified to render in TH? This would allow all elements in the header to render the same and help with styling.
Business Need - User Story Terminology:
As a Telerik Support Specialist, I would like our programmers to incorporate new code which will treat hyphens as if it were a space upon ExportToPdf() so that we gracefully handle for scenarios where a very long word with a hyphen will wrap to the next line instead of overlapping other content.
Please create a method that will convert the old expressions to new format and make them re-usable again.
I like to add my own buttons in the toolbar, for example to open new Windows, add more text to the description, specify if I like or dislike the picture.