This article lists the answers to the most frequently asked questions (FAQs) about the Kendo UI suite for Angular.
Kendo UI for Angular fully supports all browsers which are supported by the Angular framework with certain limitations for Internet Explorer 9 with regard to the styling options. For more information, refer to our article on browser compatibility.
When can I expect the same level of maturity and completeness in Kendo UI for Angular as in Kendo UI for jQuery?
The plans for the future development of the Kendo UI for Angular suite are published and regularly updated on the Roadmap page.
The Kendo UI Grid for Angular relies on the built-in browser scrollbar. For more information on how to style native scrollbars in different browsers, refer to this tutorial or this Stack Overflow thread.
Kendo UI for Angular is a new addition to the Kendo UI family of commercial products. The suite is backed by the same level of professional support and scheduled updates that are shipped by Kendo UI for jQuery.
Is it easy to use a single-code base to target desktop and mobile platforms when using Kendo UI and Ionic?
Angular facilitates the use of the “underlying plumbing” for your application that will be used across platforms. However, to target mobile, it is advisable to use NativeScript. For more information on migrating hybrid applications to native, refer to the guide on upgrading hybrid applications to native with NativeScript.
Subscribe for NPM notifications through hooks.
The new Kendo UI releases for Angular are announced on the Telerik blog.
No, but there are other cross-product options. Kendo UI for Angular ships the following themes:
All these themes are compatible with both Kendo UI for Angular and Kendo UI for jQuery components. To create a custom theme that matches the desired looks, you can also use the ThemeBuilder application.
Yes, Kendo UI for jQuery still supports AngularJS. The product was renamed only to differentiate it from Kendo UI for Angular.
The concepts and API calls of each component from Kendo UI for Angular are documented. We preserved all the API that made sense to be migrated. On the other hand, Kendo UI for Angular uses a different approach towards major features, such as data binding.
The Angular migration guide will help you convert your AngularJS knowledge into Angular mastery.
It depends on the Angular version you are targeting. For detailed information, refer to the Angular migration guide.
Yes, Kendo UI Angular supports Ahead-of-Time compilation without additional required steps. Also check the official Angular AOT compilation article.
No, but you can import all components from a single package by importing the package module. To see how to do this, check the Overview article of the specific package - for example, the Dropdowns.
The slow loading is due to the specifics of the Internet Explorer browser. However, there are ways to optimize the Grid performance.
Yes, server-side data operations are supported through the Angular HTTP client and endpoints that accept query string options.
Does the Grid for Angular support detail templates and header attributes, similar to the Grid for jQuery?
The Angular Grid is catching up fast. For more information on planned features, refer to the Roadmap.
Yes, it does. However, Kendo UI do not plan to have a DataSource component in Kendo UI for Angular. Having a DataSource component, such as the one in the Kendo UI for jQuery suite, does not fit well in the Angular context. The framework already provides most of the DataSource functionalities such as the ability to fetch data, change tracking, and others. You can also use other libraries and patterns for working with data.
Yes, it does. The ComboBox component supports a primitive AutoComplete-like functionality as well as binding to an asynchronous source. It is possible to bind to the
filterChange event of the Kendo UI ComboBox for Angular with an event handler that will debounce, query an API, and update the member bound to
[data] with the results.
Yes, you can. All available themes provide options for customization. To modify the variables of each theme, refer to these articles:
Why do I have to include the CSS for Kendo UI components? Why are CSS not included in the
@Component that is created?
Both approaches are possible. The inclusion of the CSS at the component level allows the style encapsulation of the native or emulated Shadow DOM.
You can customize the styles by using CSS overloads or SASS. For more information on the styling options, refer to the overview of our themes and styles.