Starting with the R2 2023 release, Kendo UI will no longer ship Hybrid UI components. This means that the R2 2023 will be the last release to include Kendo Hybrid in the Kendo UI package. See full announcement in Kendo jQuery blog post. The last stable version that we recommend to use for Kendo Hybrid components is R3 2022 SP1.
This is a collection of frequently asked questions (FAQ) and their answers about how Kendo UI hybrid mobile components generally work and behave on all platforms.
No. They are incompatible. The reason for this is that Kendo UI web skins do not have skin names as a class selector and their styling is affecting everything in your page and application. They also partially override the existing Kendo UI hybrid mobile platform themes. You can use them in the Hybrid UI only, if you do not use the Hybrid UI platform themes at all, including the common CSS—the web skins already have everything needed.
The Hybrid UI stylesheets need the
images subfolder to load the icon font and the Back button mask. Copy them over with your stylesheets.
Due to issues related to simultaneous handling of
touch events on hybrid devices, the Hybrid UI has strict requirements for events. You can attach your handler to the Button's own
I have several text entry forms in my application, but I experience strange issues in Android and WP8. Why?
Android has severe problems with input elements, especially when mixed with CSS3 transforms, which the hybrid mobile Kendo UI Scroller uses for faster animation. Windows Phone 8 on the other hand switches off transforms when an input element is focused, thus stopping any scrolling and resetting the scroller to top. Check the article on form elements for more information about both topics. To avoid these issues, refer to View's
useNativeScroller configuration option, or the Scroller's
useNative option, which is available as of Kendo UI Q1 2013.
The Hybrid UI framework strives to achieve native-like styling for the different platforms, hence the styling is completely different and tries to match the current device styling automatically. If you want to have the same styling on all devices, choose the one you want, and force it through the Application
This can happen when the Hybrid UI Application is initialized multiple times. For example, when the initialization occurs in the
Layout.cshtml page of an ASP.NET MVC project. The mobile application should be initialized only once to be able to function properly.
This can happen when the Hybrid UI widget is initialized multiple times. A common mistake is to build the widget at the
show event of the View. Hybrid UI widgets should be initialized only once—at the
init event of their View, or via the data-attributes in the markup.