The Dialog is part of Telerik UI for ASP.NET MVC, a
professional grade UI library with 110+ components for building modern and feature-rich applications. To try it out sign up for a free 30-day trial.
The Dialog is part of Telerik UI for ASP.NET MVC, a professional grade UI library with 110+ components for building modern and feature-rich applications. To try it out sign up for a free 30-day trial.
The Telerik UI Dialog HtmlHelper for ASP.NET MVC is a server-side wrapper for the Kendo UI Dialog widget.
The Dialog is a modal popup that brings information to the user. It also enables the user to perform specific actions by using action buttons, for example, to enter data or choose between options. If needed, the Dialog can accommodate complex UI elements that require the focus of the user. The Dialog is a subtype of the Kendo UI for jQuery Window with the most prominent differences being the added actions and predefined dialogs.
In the most common use case, the Dialog opens as a result of a user action rather than of the
load event of the page. To achieve this, you must initialize the widget as non-visible and open it when needed.
The following example demonstrates how to define the Dialog.
@(Html.Kendo().Dialog() .Name("dialog") // The name of the Dialog is mandatory. It specifies the "id" attribute of the widget. .Title("Software Update")// Set the title of the Dialog. .Content("Do you agree terms and conditions?") // Define the content of the Dialog. .Visible(false) // The widget will be initialized as invisible. )
The Dialog provides default configuration options that you can set during its initialization—height and width, custom action buttons, title, close buttons, animation effects, and so on.
The following example demonstrates a basic Dialog configuration.
- Custom action buttons—Adding action buttons to the Dialog allows you to interact with the user.
- Height and width—You can control the dimensions of the Dialog by setting its height and width. The default size of the Dialog depends on its content.
HTML structure and DOM placement—Regardless of where you initialize the UI component, the HTML code of the Dialog will be appended as a child of the document's
- Accessibility—The Dialog is accessible for screen readers, supports WAI-ARIA attributes, and delivers keyboard shortcuts for faster navigation.
- Events—The Dialog emits a variety of events that allow you to implement custom functionality.