.. _dijit/Dialog: dijit.Dialog ============ :Available: since V? :jsDoc: http://api.dojotoolkit.org/jsdoc/HEAD/dijit.Dialog .. contents:: :depth: 2 ============ Introduction ============ Dijit's modal Dialog Box simulates a regular GUI dialog box. The contents can be arbitrary HTML, but are most often a form or a short paragraph. The user can close the dialog box without acting by clicking on the X button in the top-right corner. ===== Usage ===== .. code-block :: javascript :linenos: After creating a Dialog, the Dialog (and the underlay) moves itself right behind the element within the DOM, so it can overlay the entire webpage. With this move no other elements parent the Dialog.domNode. Therefore you have to add a ``class="tundra"`` attribute (or some other applicable :ref:`theme name `) to your tag, in order to show the Dialog with the right styles: .. code-block :: html ... ... ======== Examples ======== Dialog via markup ----------------- The first example creates a Dialog via markup from an existing DOM node: .. cv-compound:: A dialog created via markup. First let's write up some simple HTML code because you need to define the place where your Dialog sdhould be created. .. cv:: html
Content of Tab "foo"
Hi, I'm Tab "boo"

When pressing this button the dialog will popup:

.. cv:: javascript :label: The javascript, put this wherever you want the dialog creation to happen Note that dialog's source markup can be hidden via specifying style="display: none", to prevent it from flashing on the screen during page load. However, hiding the dialog indirectly via a class won't work (in that the dialog will remain invisible even when it's supposed to be displayed). Dialog programmatically ----------------------- Now lets create a dialog programmatically, and change the dialog's content dynamically .. cv-compound:: A programmatically created dialog with no content. First lets write up some simple HTML code because you need to define the place where your Dialog should be created. .. cv:: html

When pressing this button the dialog will popup. Notice this time there is no DOM node with content for the dialog:

.. cv:: javascript :label: The javascript, put this wherever you want the dialog creation to happen Coloring the Underlay --------------------- If you wish to alter the default color for the underlay, you do so in CSS. The underlay receives an ID to match the Dialog, suffixed with :ref:``underlay``, which you can define a css class for: .. cv-compound:: .. cv:: html
My background color is Green

When pressing this button the dialog will popup:

.. cv:: javascript Forms and Functionality in Dialogs ---------------------------------- This example shows a Dialog containing form data. You can get the form data as a javascript object by calling attr('value') on the dialog. To prevent the user from dismissing the dialog if there are errors in the form, add an onClick handler to your submit button. In order to run Dialog's execute-method the submit button has to be a dijit.form.Button, normal submit button doesn't trigger this function. In addition, the form has to be local, the dialog doesn't find the form values if it's included via href attribute. To simply close the dialog, click the Cancel button, which calls the hide() function on the Dialog. .. cv-compound:: .. cv:: html

When pressing this button the dialog will popup:

.. cv:: javascript :label: The javascript, put this wherever you want the dialog creation to happen External Dialog content using HREF attribute -------------------------------------------- You can also load dialog content from another page by setting HREF attribute for the widget. Note that the Dialog doesn't execute script tags inline external content. However, it parses the page for widgets, so you can add functionality to widgets by connecting into widget extension points using declarative markup (DojoML; e.g. `` .. cv:: html

When pressing this button the dialog will popup loading the dialog content using an XHR call.

Sizing the Dialog ----------------- A dialog by default sizes itself according to it's content, just like a plain
. If you want a scrollbar on a dialog, then you need to add width/height to a div *inside* the dialog, like this: .. cv-compound:: .. cv:: javascript .. cv:: html

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean semper sagittis velit. Cras in mi. Duis porta mauris ut ligula. Proin porta rutrum lacus. Etiam consequat scelerisque quam. Nulla facilisi. Maecenas luctus venenatis nulla. In sit amet dui non mi semper iaculis. Sed molestie tortor at ipsum. Morbi dictum rutrum magna. Sed vitae risus.

When pressing this button the dialog will popup (with a scrollbar):

============= Accessibility ============= Keyboard -------- ==================================================== ================================================= Action Key ==================================================== ================================================= Navigate to next focusable element in the dialog tab Navigate to previous focusable element in the dialog shift-tab Close the dialog escape ==================================================== ================================================= Keyboard Navigation in Release 1.1 and later ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When a dialog is opened focus goes to the first focusable element within the dialog. The first focusable element may be an element which appears in the tab order by default such as a form field or link, an element with a tabindex attribute value of 0 or an element with a tabindex value greater than 0. Elements with a tabindex value greater than 0 will appear in the tab order before elements with a tabindex of 0 or those in the tab order by default. If the dialog does not contain a focusable item, focus will be set to the dialog container element when the dialog is opened. The same focus behavior has been implemented for tooltip dialog When focus is in a dialog, pressing the tab key will move focus forward to each focusable element within the dialog. When focus reaches the last focusable element in the dialog, pressing tab will cycle focus back to the first focusable item. Pressing shift-tab will move focus backwards through focusable elements within the dialog. When the first focusable item is reached, pressing shift-tab will move focus to the last focusable item in the dialog. Keyboard Navigation Previous to Release 1.1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When a dialog is opened focus goes to the title section of the dialog. This was implemented to provide screen reader support to speak the title of the dialog when it is opened. Likewise, when a tooltip dialog is opened, focus is placed on the container of the tooltip dialog. In future versions of the dialog and tooltip dialog widgets, focus will go to the first item in the dialog or tooltip dialog. When focus is in a dialog, pressing the tab key will move focus forward to each focusable element within the dialog. When focus reaches the last focusable element in the dialog, pressing tab will cycle focus back to the dialog title. Pressing shift-tab will move focus backwards through focusable elements within the dialog until the dialog title is reached. If focus has previous cycled forward through all of the elements, pressing shift-tab with focus on the dialog title will move focus to the last element in the dialog. If focus has not previously been cycled through all of the focusable elements in the dialog using the tab key, pressing shift-tab with focus on the dialog title will leave focus in the title. The same focus cycling applies to the tooltip dialog as well with focus being set to the tooltip dialog container since there is no dialog title. Improved Screen Reader Support in 1.4 ------------------------------------- The dialog now supports the aria-describedby property. If you have a description of the dialog that you would like spoken by the screen reader when the dialog opens add the aria-describedby property to the dialog. Include an element containing the text you want spoken in the dialog. The value of the aria-describedby property is the id of the element containing the text. .. code-block :: javascript
Text to describe dialog
Additional dialog contents....
For earlier Dojo versions, you can add an onshow event handler that adds the aria-describedby property: .. code-block :: javascript
Text to describe dialog
Additional dialog contents....
Known Issues ------------ * On Windows, In Firefox 2, when in High Contrast mode, the dialog with display correctly, but the underlying page will not be seen. * Dialogs with an input type=file as the only focusable element will not work with the keyboard. This is because input type=file elements require two tab stops - one in the textbox and the other on the "Browse" button. Rather than clutter the dialog box widget with code to special case for this one condition, dialog boxes with an input type=file as the only focusable element are not supported. * Dialogs with an input type=file element as the first focusable element in Firefox (and there are additional focusable elements). Programmatically setting focus to an input type=file element behaves oddly in Firefox. In this case the focus is set onto the textbox field and then immediately moved onto the browse button of the input type=file field. This causes problems in Firefox when setting focus to an input type=file element as the first element as a dialog. For this reason, in Firefox if the first focusable item in a dialog is an input type=file, focus will be set onto the dialog container rather than the input element. For these reasons it is recommended that input type=file elements not be added as the only or first focusable item within a dialog in Firefox. * Even though the dialog is marked with the proper ARIA role of dialog, there are issues with screen readers. Due to these issues , it is important that the instructions or label for a trigger element that opens a dialog to indicate via text that a dialog will be opened. * JAWS 9 does not speak "dialog" when the dialog is opened in Firefox or IE 8. * In Firefox 2 even though the focus is on the first focusable item in the dialog, the information about that item is also not spoken. * In Firefox 3 with JAWS 9 the dialog is also not announced but the information about the item in the dialog which gets focus is spoken. The issue has been fixed in JAWS 10 with Firefox 3. * In IE 8 with JAWS 10 the dialog information and title is not spoken. This is due to the fact that IE 8 does not support the ARIA labelledby property that is used to assign the title to the dialog. * There are focus issues when the dialog is created via an href. Due to timing issues focus may not be properly set nor properly trapped in the dialog. For accessibility reasons, dialogs created via href are not recommended. This issue will be addressed in a future release. * When loading Dialog content with the href property, there can be issues with scrolling in IE7: If the loaded content contains dijit.layout elements and the Dialog content is larger than the size of the dialog, the layout dijits do not scroll properly in IE7. The workaround for this issue is to set the 'position:relative' style to the dialog.containerNode: * Dialogs with no focusable items cause problems for screen readers. If the dialog has no focusable items, set the tabindex="0" on the container element of the text. This will set focus to that container when the dialog is opened and will cause JAWS to speak the title of the dialog and the user will know that a dialog has been opened. .. code-block :: javascript :linenos: dialogObj = new dijit.Dialog({ id: 'dialogWithHref', title: 'The title' href: "/url/to/dialog/content/including/layout/dijit/", }); dojo.style(dialogObj.containerNode, { position:'relative', });