dijit.Dialog¶
| Available: | since V? |
|---|---|
| jsDoc: | http://api.dojotoolkit.org/jsdoc/HEAD/dijit.Dialog |
Contents
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¶
1 2 3 4 5 6 7 8 9 | <script type="text/javascript">
dojo.require("dijit.Dialog");
// create the dialog:
myDialog = new dijit.Dialog({
title: "My Dialog",
content: "test content",
style: "width: 300px"
});
</script>
|
After creating a Dialog, the Dialog (and the underlay) moves itself right behind the <body> 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 theme name) to your <body> tag, in order to show the Dialog with the right styles:
<html>
<head>
...
</head>
<body class="tundra">
...
</body>
Examples¶
Dialog via markup¶
The first example creates a Dialog via markup from an existing DOM node:
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.
<div id="dialogOne" dojoType="dijit.Dialog" title="My Dialog Title">
<div dojoType="dijit.layout.TabContainer" style="width: 200px; height: 300px;">
<div dojoType="dijit.layout.ContentPane" title="foo">Content of Tab "foo"</div>
<div dojoType="dijit.layout.ContentPane" title="boo">Hi, I'm Tab "boo"</div>
</div>
</div>
<p>When pressing this button the dialog will popup:</p>
<button id="buttonOne" dojoType="dijit.form.Button" type="button">Show me!
<script type="dojo/method" event="onClick" args="evt">
// Show the Dialog:
dijit.byId("dialogOne").show();
</script>
</button>
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
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.
<p>When pressing this button the dialog will popup. Notice this time there is no DOM node with content for the dialog:</p>
<button id="buttonTwo" dojoType="dijit.form.Button" onClick="showDialogTwo();" type="button">Show me!</button>
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:
<style type="text/css">
#dialogColor_underlay {
background-color:green;
}
</style>
<div id="dialogColor" title="Colorful" dojoType="dijit.Dialog">
My background color is Green
</div>
<p>When pressing this button the dialog will popup:</p>
<button id="button4" dojoType="dijit.form.Button" type="button">Show me!</button>
<script type="text/javascript">
dojo.require("dijit.form.Button");
dojo.require("dijit.Dialog");
dojo.addOnLoad(function(){
// create the dialog:
var dialogColor = dijit.byId("dialogColor");
// connect t the button so we display the dialog onclick:
dojo.connect(dijit.byId("button4"), "onClick", dialogColor, "show");
});
</script>
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.
<div dojoType="dijit.Dialog" id="formDialog" title="Form Dialog"
execute="alert('submitted w/args:\n' + dojo.toJson(arguments[0], true));">
<table>
<tr>
<td><label for="name">Name: </label></td>
<td><input dojoType="dijit.form.TextBox" type="text" name="name" id="name"></td>
</tr>
<tr>
<td><label for="loc">Location: </label></td>
<td><input dojoType="dijit.form.TextBox" type="text" name="loc" id="loc"></td>
</tr>
<tr>
<td><label for="date">Start date: </label></td>
<td><input dojoType="dijit.form.DateTextBox" type="text" name="sdate" id="sdate"></td>
</tr>
<tr>
<td><label for="date">End date: </label></td>
<td><input dojoType="dijit.form.DateTextBox" type="text" name="edate" id="edate"></td>
</tr>
<tr>
<td><label for="date">Time: </label></td>
<td><input dojoType="dijit.form.TimeTextBox" type="text" name="time" id="time"></td>
</tr>
<tr>
<td><label for="desc">Description: </label></td>
<td><input dojoType="dijit.form.TextBox" type="text" name="desc" id="desc"></td>
</tr>
<tr>
<td align="center" colspan="2">
<button dojoType="dijit.form.Button" type="submit"
onClick="return dijit.byId('formDialog').isValid();">OK</button>
<button dojoType="dijit.form.Button" type="button"
onClick="dijit.byId('formDialog').hide();">Cancel</button>
</td>
</tr>
</table>
</div>
<p>When pressing this button the dialog will popup:</p>
<button id="buttonThree" dojoType="dijit.form.Button" type="button">Show me!</button>
If you want to handle the onSubmit event like a traditional <form> element, you will need to employ a <form> either as a traditional HTML element or as a ''dijit.form.Form''. This example shows a Dialog with an embedded Form which handles the onSubmit event, validation, and an xhrPost to the server.
<div dojoType="dijit.Dialog" id="formDialog2" title="Form Dialog" style="display: none">
<form dojoType="dijit.form.Form">
<script type="dojo/event" event="onSubmit" args="e">
dojo.stopEvent(e); // prevent the default submit
if (!this.isValid()) { window.alert('Please fix fields'); return; }
window.alert("Would submit here via xhr");
// dojo.xhrPost( {
// url: 'foo.com/handler',
// content: { field: 'go here' },
// handleAs: 'json'
// load: function(data) { .. },
// error: function(data) { .. }
// });
</script>
<div class="dijitDialogPaneContentArea">
<label for='foo'>Foo:</label><div dojoType="dijit.form.ValidationTextBox" required="true"></div>
</div>
<div class="dijitDialogPaneActionBar">
<button dojoType="dijit.form.Button" type="submit">OK</button>
<button dojoType="dijit.form.Button" type="button"
onClick="dijit.byId('formDialog2').hide();">Cancel</button>
</div>
</form>
</div>
<p>When pressing this button the dialog will popup:</p>
<button id="buttonThree" dojoType="dijit.form.Button" type="button">Show me!</button>
Terms and Conditions Dialog¶
This example shows a Dialog that will ask the user to accept or decline the terms and conditions.
<div dojoType="dijit.Dialog" id="formDialog" title="Accept or decline agreement terms" execute="alert('submitted w/args:\n' + dojo.toJson(arguments[0], true));">
<h1>Agreement Terms</h1>
<div dojoType="dijit.layout.ContentPane" style="width:400px; border:1px solid #b7b7b7; background:#fff; padding:8px; margin:0 auto; height:150px; overflow:auto; ">
Dojo is available under *either* the terms of the modified BSD license *or* the Academic Free License version 2.1. As a recipient of Dojo, you may choose which license to receive this code under (except as noted in per-module LICENSE files). Some modules may not be the copyright of the Dojo Foundation. These modules contain explicit declarations of copyright in both the LICENSE files in the directories in which they reside and in the code itself. No external contributions are allowed under licenses which are fundamentally incompatible with the AFL or BSD licenses that Dojo is distributed under. The text of the AFL and BSD licenses is reproduced below. ------------------------------------------------------------------------------- The "New" BSD License: ********************** Copyright (c) 2005-2010, The Dojo Foundation All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
</div>
<br>
<table>
<tr>
<td>
<input type="radio" dojoType="dijit.form.RadioButton" name="agreement" id="radioOne" value="accept" onclick="accept"/>
<label for="radioOne">
I accept the terms of this agreement
</label>
</td>
</tr>
<tr>
<td>
<input type="radio" dojoType="dijit.form.RadioButton" name="agreement" id="radioTwo" value="decline" onclick="decline"/>
<label for="radioTwo">
I decline
</label>
</td>
</tr>
</table>
</div>
<p>
When pressing this button the dialog will popup:
</p>
<label id="decision" style="color:#FF0000;">
Terms and conditions have not been accepted.
</label>
<button id="termsButton" dojoType="dijit.form.Button" type="button">
View terms and conditions to accept
</button>
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. <script type="dojo/method" event="onClick">). Other options for executing scripts are iFrame and dojox.layout.ContentPane.
| height: | 500 |
|---|
<script type="text/javascript">
dojo.require("dijit.form.Button");
dojo.require("dijit.Dialog");
</script>
<div id="external" dojoType="dijit.Dialog" title="My external dialog" href="{{dataUrl}}dojo/resources/LICENSE" style="overflow:auto; width: 400px; height: 200px;">
</div>
<p>When pressing this button the dialog will popup loading the dialog content using an XHR call.</p>
<button dojoType="dijit.form.Button" onClick="dijit.byId('external').show();" type="button">Show me!</button>
Sizing the Dialog¶
A dialog by default sizes itself according to it's content, just like a plain <div>. If you want a scrollbar on a dialog, then you need to add width/height to a div inside the dialog, like this:
<script type="text/javascript">
dojo.require("dijit.form.Button");
dojo.require("dijit.Dialog");
</script>
<div id="sized" dojoType="dijit.Dialog" title="My scrolling dialog">
<div style="width: 200px; height: 100px; overflow: auto;">
<p>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.</p>
</div>
</div>
<p>When pressing this button the dialog will popup (with a scrollbar):</p>
<button dojoType="dijit.form.Button" onClick="dijit.byId('sized').show();" type="button">Show me!</button>
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 |
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.
<div dojoType="dijit.Dialog" title="Example Dialog" aria-describedby="intro">
<div id="intro">Text to describe dialog</div>
<div>Additional dialog contents....</div>
</div>
For earlier Dojo versions, you can add an onshow event handler that adds the aria-describedby property:
<div dojoType="dijit.Dialog" title="Example Dialog" onShow="dojo.attr(this.domNode, 'aria-describedby', 'info');">
<div id="intro">Text to describe dialog</div>
<div>Additional dialog contents....</div>
</div>
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 and JAWS 11 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 has been addressed in the 1.5 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 an iframe as the contents will cause a focus trap and are not supported. This because the dialog code can not traverse within the iframe contents to find all of the focusable elements to know the first and last focusable element within the contents.
- 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.
1 2 3 4 5 6 7 8 9 | dialogObj = new dijit.Dialog({
id: 'dialogWithHref',
title: 'The title'
href: "/url/to/dialog/content/including/layout/dijit/",
});
dojo.style(dialogObj.containerNode, {
position:'relative',
});
|