Completed
Last Updated: 19 Oct 2026 14:25 by ADMIN
Release 2026 Q3 SP1
ADMIN
Ianko
Created on: 15 Nov 2016 15:03
Category: UI for ASP.NET AJAX
Type: Bug Report
1
Missing TS definition for Telerik.Web.UI.d.ts
There are missing methods in the TypeScript definitions provided. 

You can find attached a file that illustrates what needs to be updated.
2 comments
ADMIN
Rumen
Posted on: 19 Oct 2026 14:20
Hello everyone,

We have revisited this report and updated the TypeScript definitions file (Telerik.Web.UI.d.ts). The following members from the attached file are now covered:

- $telerik.isTouchDevice, isSafari, isIE and isOpera are declared as boolean properties instead of methods.
- $telerik.$ (the jQuery reference) is declared.
- AjaxRequestEventArgs.set_enableAjax accepts a boolean value and returns void.
- RadListBox.get_checkAllCheckBox() is declared and returns the checkbox element.
- RadAsyncUpload.Modules.FileApi.isAvailable() is declared.
- RadContextMenu.show() and hide() are declared.

Some of the other members from the attachment were already present in the file in the meantime: RadMenuItem get_navigateUrl and set_navigateUrl, FileExplorerItem.get_path, the ToolBarSingleClick enum, and the add_showing and add_hidden methods of RadContextMenu. Methods such as RadListBox.get_checkedItems and RadAsyncUpload.getUploadedFiles are typed as any, so they can be used with your own typings.

A few members were not added because they are either internal or do not exist in the client-side code: RadToolBarItem._processClickPostBackLogic, GridDataItem.Attributes, and get_item and get_menuItem on RadContextMenuCancelEventArgs.

The updated definitions will be available in 2026 Q3 SP1.

 

Regards,
Rumen
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources! 
ADMIN
Rumen
Posted on: 03 Nov 2025 09:39

Hi everyone,

This behavior was originally reported over 9 years ago and has not seen significant demand or follow-up from the community since then. Given this and the need to focus on higher-impact and more frequently requested improvements, we are closing this case.

If this limitation is still affecting your scenario, please share additional details or use cases. Your feedback will help us better evaluate the priority of this request in the future. Thank you for your understanding and contributions!

Best regards,
Rumen