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 the 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 the scrollbar in Internet Explorer, WebKit (Safari, Google Chrome), and Opera, refer to this issue on Stack Overflow.
No, the entire product is distributed under a commercial license. To explore its full functionality, you are welcome to register for a free 30-day trial, which also grants access to our outstanding technical support that Kendo UI for jQuery is known for.
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, you cannot. Kendo UI for Angular ships the following themes which you can use to style your project:
All available themes are compatible with both Kendo UI for Angular and Kendo UI for jQuery components. To create a theme that matches the looks of your desired project, you can also use the ThemeBuilder application.
Yes, it does. Kendo UI for jQuery is the same product it has always been. The product acquired the Kendo UI for jQuery name to differentiate it from Kendo UI for Angular.
The conceptual aspects as well as the API calls of each component from the Kendo UI for Angular suite are documented. All API configurations that made sense to migrate to the new suite are preserved. However, the approaches Kendo UI for Angular uses towards major features, such as data binding, are different.
For detailed information on how to convert your AngularJS knowledge into Angular mastery, refer to the migration guide on Angular.
It depends on what version of Angular you are currently targeting. For detailed information, refer to the migration guide on Angular.
No, you cannot. However, you can import all components within a package by importing the package module. For more information on how to do this, refer to the Overview article of the specific Kendo UI package for Angular—for example, the Dropdowns.
The slow loading is due to the specifics of the Internet Explorer browser. For more information on how to optimize the process, refer to the article on the browser performance of the Grid.
Yes, it does. Server-side operations are supported through the Angular HTTP client and endpoints that accept query string options.
Does the Grid for Angular support the same attributes, such as header attributes and detail templates, as the Grid for jQuery?
No, they are not. 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 the articles on:
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.
To set up Angular to work with Visual Studio, refer to the documentation by the Angular team. To integrate Kendo UI for Angular, follow the steps in the article on getting started with Kendo UI for Angular.
You can customize the styles by using CSS overloads or SASS. For more information on the styling options, refer to the introductory article on themes and styles.