The MenuNav Node Plugin makes it easy to transform existing list-based markup into traditional, drop down navigational menus that are both accessible and easy to customize, and only require a small set of dependencies. The MenuNav Node Plugin features:

Progressive Enhancement: The MenuNav Node Plugin is designed to support Progressive Enhancement, making it easy to transform simple, semantic markup into dynamic drop-down menus with just a few lines of JavaScript.
Small footprint: The MenuNav Node Plugin has a small footprint of ~5 KB (GZIP'd) and requires a minimal set of dependencies.
Accessibility & Usability Minded: The MenuNav Node Plugin was built with both accessibility and usability in mind. The MenuNav Node Plugin implements established mouse and keyboard interaction patterns to deliver a user experience that is both familiar and easy to use. To that foundation the MenuNav Node plugin adds support for screen readers through the use of the WAI-ARIA Roles and States.
Easy to style and configure: The MenuNav Node Plugin is easy to configure. The visual presentation of menus is controlled completely via CSS. A handful of straightforward [[#configuration attributes]] can be used to make common modifications to a menu's behavior.
`` Shim for IE 6</dt> <dd> No menuing system would be complete without an `<iframe>` to prevent `<select>` elements from poking through menus in IE 6. </dd> </dl> </div> {{>getting-started}} {{>need-skin-note}} ``` <body class="yui3-skin-sam"> {{>need-skin-comment}} ``` <h3 id="setup">Basic Setup</h3> <p> To create a menu using the MenuNav Node Plugin, start by including the required markup. The markup for menus created using the MenuNav Node Plugin follows the same <a href="../widget/index.html#markup">pattern established for Widgets</a>, with each menu's content box containing one or more `<ul>` elements: </p> <h4>Menu Markup Example</h4> ``` <div id="menu-1" class="yui3-menu"> <div class="yui3-menu-content"> <ul>  </ul> </div> </div> ``` <p> Menu items also follow the Widget markup pattern, with the root node defined using an `<li>` element: </p> <h4>MenuItem Markup Example</h4> ``` <li class="yui3-menuitem"> <a class="yui3-menuitem-content" href="http://www.yahoo.com"> Yahoo! </a> </li> ``` <p> Submenus are defined by wrapping the the menu markup in an <code><li></code> element. Each submenu must have have a label. The label should preceed the menu markup, and the label's <code>href</code> attribute should be set to the point to the id of its corresponding submenu. </p> <h4>Submenu Markup Example</h4> ``` <li> <a class="yui3-menu-label" href="#submenu-1">Submenu Label</a> <div id="submenu-1" class="yui3-menu"> <div class="yui3-menu-content"> <ul>  </ul> </div> </div> </li> ``` <p> Following the patterns illustrated above, the markup for a menu created using the MenuNav Node Plugin comes together as follows: </p> ``` <div id="menu-1" class="yui3-menu"> <div class="yui3-menu-content"> <ul> <li class="yui3-menuitem"> <a class="yui3-menuitem-content" href="http://www.yahoo.com"> Yahoo! </a> </li> <li> <a class="yui3-menu-label" href="#pim">PIM</a> <div id="pim" class="yui3-menu"> <div class="yui3-menu-content"> <ul> <li class="yui3-menuitem"> <a class="yui3-menuitem-content" href="http://mail.yahoo.com">Yahoo! Mail</a> </li> <li class="yui3-menuitem"> <a class="yui3-menuitem-content" href="http://addressbook.yahoo.com">Yahoo! Address Book</a> </li> <li class="yui3-menuitem"> <a class="yui3-menuitem-content" href="http://calendar.yahoo.com">Yahoo! Calendar</a> </li> <li class="yui3-menuitem"> <a class="yui3-menuitem-content" href="http://notepad.yahoo.com">Yahoo! Notepad</a> </li> </ul> </div> </div> </li> </ul> </div> </div> ``` <p> With the markup for the menu in place, simply get a Node reference for the root menu and then call the <a href="{{apiDocs}}/classes/Node.html#method_plug"><code>plug</code></a> method, passing in a reference to the MenuNav Node Plugin. </p> ``` // Call the "use" method, passing in "node-menunav". This will load the // script and CSS for the MenuNav Node Plugin and all of the required // dependencies. YUI().use("node-menunav", function(Y) { // Use the "contentready" event to initialize the menu when the subtree of // element representing the root menu (<div id="menu-1">) is ready to // be scripted. Y.on("contentready", function () { // The scope of the callback will be a Node instance representing // the root menu (<div id="menu-1">). Therefore, since "this" // represents a Node instance, it is possible to just call "this.plug" // passing in a reference to the MenuNav Node Plugin. this.plug(Y.Plugin.NodeMenuNav); }, "#menu-1"); }); ``` <h2 id="using">Using the MenuNav Node Plugin</h2> <h3 id="orientation-style-behavior">Orientation, Style and Behavior</h3> <h4>Configuring Orientation</h4> <p> The root menu of menus built using the MenuNav Node Plugin can have a verical or horizontal orientation. The default orientation for menus is vertical, but can be easily switched to horizontal by applying a class of <code>yui3-menu-horizontal</code> to the node representing the root menu's bounding box, as illustrated in the following example: </p> ``` <div id="menu-1" class="yui3-menu yui3-menu-horizontal"> <div class="yui3-menu-content"> <ul>  </ul> </div> </div> ``` <p> Once the <code>yui3-menu-horizontal</code> class name is applied to the node representing the root menu's bounding box, the menu's keyboard interaction is automatically adjusted for a horizontal orientation. The default "Sam" skin provides the following default visualization for horizontal menus, as illustrated in the follow screen capture of a horizontal menu example: </p> <div class="wideimage"><img src="{{componentAssets}}/horizontal-menu.png" width="495" height="130" alt="Screenshot of a horizontal menu rendered with the default Sam Skin"></div> <h4>Configuring Style & Behavior</h4> <p> The default "Sam" skin provides two additional visualizations for horizontal menus, each of which can be applied by both changes to the menu label markup and through the application of a class to the node representing the root menu's bounding box. </p> <h5>Menu Button Visualization</h5> <p> The first of the two optional horizontal menu visualizations available with the "Sam" skin renders each menu label as a menu button; each menu label is rendered with an arrow to the right of its text label, providing a visual cue that there is a corresponding submenu. </p> <div class="wideimage"><img src="{{componentAssets}}/menubutton-menu.png" width="495" height="130" alt="Screen capture of a horizontal menu with each menu label in the root menu rendered as menu buttons."></div> <p> To apply this style to a horizontal menu, start by adding the class <code>yui3-menubuttonnav</code> to the node representing the root menu's bounding box, as illustrated in the following example: </p> ``` <div id="menu-1" class="yui3-menu yui3-menu-horizontal yui3-menubuttonnav"> <div class="yui3-menu-content"> <ul>  </ul> </div> </div> ``` <p>Next, wrap the text node of each menu label in an <code><em></code> element:</p> ``` <div id="menu-1" class="yui3-menu yui3-menu-horizontal yui3-menubuttonnav"> <div class="yui3-menu-content"> <ul> <li> <a class="yui3-menu-label" href="#submenu-1"><em>Submenu Label</em></a> <div id="submenu-1" class="yui3-menu"> <div class="yui3-menu-content">  </div> </div> </li> </ul> </div> </div> ``` <p> As a final, optional step, use the <a href="{{apiDocs}}/classes/plugin.NodeMenuNav.html#attr_autoSubmenuDisplay"><code>autoSubmenuDisplay</code></a> and <a href="{{apiDocs}}/classes/plugin.NodeMenuNav.html#attr_mouseOutHideDelay"><code>mouseOutHideDelay</code></a> configuration attributes to configure the menu labels to behave like menu buttons. Set the <code>autoSubmenuDisplay</code> to <code>false</code>, so that each menu label's submenu isn't made visible until the label is clicked. Set the <code>mouseOutHideDelay</code> to <code>0</code> so that a label's submenu is only hidden when the user mouses down on an area outside of the submenu. </p> ``` // Call the "use" method, passing in "node-menunav". This will load the // script and CSS for the MenuNav Node Plugin and all of the required // dependencies. YUI().use("node-menunav", function(Y) { // Use the "contentready" event to initialize the menu when the subtree of // element representing the root menu (<div id="menu-1">) is ready to // be scripted. Y.on("contentready", function () { // The scope of the callback will be a Node instance representing // the root menu (<div id="menu-1">). Therefore, since "this" // represents a Node instance, it is possible to just call "this.plug" // passing in a reference to the MenuNav Node Plugin. this.plug(Y.Plugin.NodeMenuNav, { autoSubmenuDisplay: false, mouseOutHideDelay: 0 }); }, "#menu-1"); }); ``` <h5>Split Button Visualization</h5> <p> The other optional horizontal menu visualization available with the "Sam" skin renders each menu label as a split button. </p> <div class="wideimage"><img src="{{componentAssets}}/splitbutton-menu.png" width="495" height="130" alt="Screen capture of a horizontal menu with each menu label in the root menu rendered as split buttons."></div> <p>To apply this style to a horizontal menu, start by adding the class <code>yui3-splitbuttonnav</code> to the node representing the root menu's bounding box, as illustrated in the following example: </p> ``` <div id="menu-1" class="yui3-menu yui3-menu-horizontal yui3-splitbuttonnav"> <div class="yui3-menu-content"> <ul>  </ul> </div> </div> ``` <p> Next, define the markup for each menu label. Start with a <code><span></code> with a class of <code>yui3-menu-label</code> applied. Inside the <code><span></code>, place two <code><a></code> elements  one for each of the label's two clickable regions. Each <code><a></code> has separate, but related responsibilities: The first <code><a></code> represents the label's default action. The second <code><a></code> toggles the display of a submenu whose content contains other options related to, or in the same category as the default action. Therefore to configure the first <code><a></code>, simply set its <code>href</code> attribute to any URL. For the second <code><a></code>, apply a class name of <code>yui3-menu-toggle</code>, and set the value of the <code>href</code> attribute to the id of the label's corresponding submenu. Lastly, the text node of the second <code><a></code> should label the contents of its corresponding submenu. </p> ``` <div id="menu-1" class="yui3-menu yui3-menu-horizontal yui3-splitbuttonnav"> <div class="yui3-menu-content"> <ul> <li> <span class="yui3-menu-label"> <a href="http://answers.yahoo.com">Answers</a> <a href="#answers-options" class="yui3-menu-toggle">Answers Options</a> </span> <div id="answers-options" class="yui3-menu"> <div class="yui3-menu-content"> <ul> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://answers.yahoo.com/dir/">Answer</a></li> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://answersonthestreet.yahoo.com/">Answers on the Street</a></li> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://answers.yahoo.com/question/;_ylt=Av3Nt22Mr7YNs651NWFv8YUPzKIX;_ylv=3?link=ask">Ask</a></li> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://answers.yahoo.com/dir/;_ylt=Aqp_jJlsYDP7urcq2WGC6HBJxQt.;_ylv=3?link=over&amp;more=y">Discover</a></li> </ul> </div> </div> </li> </ul> </div> </div> ``` <p> Use the <a href="{{apiDocs}}/classes/plugin.NodeMenuNav.html#attr_autoSubmenuDisplay"><code>autoSubmenuDisplay</code></a> and <a href="{{apiDocs}}/classes/plugin.NodeMenuNav.html#attr_mouseOutHideDelay"><code>mouseOutHideDelay</code></a> configuration attributes to configure the menu labels to behave like split buttons. Set the <code>autoSubmenuDisplay</code> to <code>false</code>, so that each menu label's submenu isn't made visible until the menu trigger is clicked. Set the <code>mouseOutHideDelay</code> to <code>0</code> so that a label's submenu is only hidden when the user mouses down on an area outside of the submenu. </p> ``` // Call the "use" method, passing in "node-menunav". This will load the // script and CSS for the MenuNav Node Plugin and all of the required // dependencies. YUI().use("node-menunav", function(Y) { // Use the "contentready" event to initialize the menu when the subtree of // element representing the root menu (<div id="menu-1">) is ready to // be scripted. Y.on("contentready", function () { // The scope of the callback will be a Node instance representing // the root menu (<div id="menu-1">). Therefore, since "this" // represents a Node instance, it is possible to just call "this.plug" // passing in a reference to the MenuNav Node Plugin. this.plug(Y.Plugin.NodeMenuNav, { autoSubmenuDisplay: false, mouseOutHideDelay: 0 }); }, "#menu-1"); }); ``` <h5>MenuItem Separators</h5> <p> The MenuNav Node Plugin makes it easy to create separators between items in a menu. To separate items in a menu, simply place items in their own `<ul>` elements inside their parent menu's content box, and apply a class name of <code>first-of-type</code> to the first `<ul>`. The following code will render separators between the "Zimbra" and "Address Book" items, and the "Notepad" and "Messenger" items. </p> ``` <div id="pim" class="yui3-menu"> <div class="yui3-menu-content"> <ul class="first-of-type"> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://mail.yahoo.com">Mail</a></li> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://www.zimbra.com">Zimbra</a></li> </ul> <ul> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://addressbook.yahoo.com">Address Book</a></li> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://calendar.yahoo.com">Calendar</a></li> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://notepad.yahoo.com">Notepad</a></li> </ul> <ul> <li class="yui3-menuitem"><a class="yui3-menuitem-content" href="http://messenger.yahoo.com">Messenger</a></li> </ul> </div> </div> ``` <p> With the separator markup in place, the default "Sam" skin will render a top border between each `<ul>` element, as illustrated in the following screen capture of one of the MenuNav Node Plugin examples: </p> <div class="wideimage"><img src="{{componentAssets}}/menuitem-separators.png" width="495" height="250" alt="Screen capture of a horizontal menu"></div> <h3>Styling State</h3> <p> The MenuNav Node Plugin manages the state of a menu's descendants through the application and removal of class names. Class names representing state are constructed using the descendent's name followed by a suffix representing the state. For example, hidden submenus have a class of <code>yui3-menu-hidden</code>. Class names used to represent state are always applied to the descendant's root node. See the [[#CSS reference]] for the complete list of state class names. </p> <h4>Active vs. Inactive</h4> <p> Menuitems and menu labels have a default (inactive) state and an active state. Menuitems and menu labels are considered active when the user is interacting with them via the keyboard or the mouse. The active class name applied to menuitems and menu labels has two benefits: It provides a single entry point for styling state that would otherwise require the use of multiple CSS pseudo classes (<code>:hover</code> and <code>:focus</code>). The second benefit to the use of the active class name is that it provides consistent styling of state across all types of elements in all <a href="http://yuilibrary.com/yui/docs/tutorials/gbs/">supported browsers</a>. (IE 6 only supports the <code>:hover</code> and <code>:focus</code> pseudo classes on <code><a></code> elements. And while IE 7 supports <code>:hover</code> on all elements, it only supports <code>:focus</code> pseudo class on <code><a></code> elements.) </p> <h4>Visible vs. Hidden</h4> <p> By default all submenus are hidden and that state is reflected by the application of the <code>yui3-menu-hidden</code> class name. If the <code>yui3-menu-hidden</code> class name is not applied to the bounding box node of all submenus, it will automatically be applied by the MenuNav's constructor. When a submenu is visible, the <code>yui3-menu-hidden</code> class name is removed and a class <code>yui3-menu-label-menuvisible</code> is applied to the submenu's corresponding label. </p> <h3>Configuration Attributes</h3> <p> The MenuNav Node Plugin has several configuration attributes that can be set via an object literal that is passed as a second argument to a Node instance's <a href="{{apiDocs}}/classes/Node.html#method_plug"><code>plug</code></a> method. (<em>Note:</em> These attributes are <em>case sensitive</em>.) In the following example, the value of the <code>mouseOutHideDelay</code> attribute is set to 1000. </p> ``` var oMenuNav = Y.one("#productsandservices"); oMenuNav.plug(Y.Plugin.NodeMenuNav, { mouseOutHideDelay: 1000 }); ``` <p>The complete list of the MenuNav Node Plugin configuration attributes are:</p> <table> <thead> <tr> <th>Name</th> <th>Default Value</th> <th>Description</th> </tr> </thead> <tbody> <tr id="usearia"> <td>useARIA</td> <td>True</td> <td>Boolean indicating if use of the WAI-ARIA Roles and States should be enabled for the MenuNav. Set to true by default for Firefox 3 and Internet Explorer 8 as currently only these browsers have support for ARIA, and are supported by several screen readers for Windows that also offer support for ARIA.</td> </tr> <tr id="autosubmenudisplay"> <td>autoSubmenuDisplay</td> <td>True</td> <td>Boolean indicating if submenus are automatically made visible when the user mouses over the menu's items.</td> </tr> <tr id="submenushowdelay"> <td>submenuShowDelay</td> <td>250</td> <td>Number indicating the time (in milliseconds) that should expire before a submenu is made visible when the user mouses over the menu's label. </td> </tr> <tr id="submenuhidedelay"> <td>submenuHideDelay</td> <td>250</td> <td>Number indicating the time (in milliseconds) that should expire before a submenu is hidden when the user mouses out of a menu label heading in the direction of a submenu.</td> </tr> <tr id="mouseouthidedelay"> <td>mouseOutHideDelay</td> <td>750</td> <td>Number indicating the time (in milliseconds) that should expire before a submenu is hidden when the user mouses out of it.</td> </tr> </tbody> </table> <h3>Handling Events</h3> <p> The MenuNav Node Plugin publishes no custom events of its own. To listen for any DOM-related events for a menu built using the MenuNav Node Plugin, use the <a href="{{apiDocs}}/classes/Node.html#method_on"><code>on</code></a> method of the plugin's host Node instance. The following example illustrates how to listen for the <code>click</code> event of menu a built using the MenuNav Node Plugin: </p> ``` // Get a Node instance for HTML element var oMenuNode = Y.one("#menu-nav-1"); // Apply the MenuNav Node Plugin to the Node instance oMenuNode.plug(Y.Plugin.NodeMenuNav); // Register a "click" event listener to the Node instance using the "on" method oMenuNode.on("click", function () { alert("here"); }); ``` <p>For additional information on listening for DOM-related events, see the <a href="../node/index.html#node-events">DOM Events</a> section of the <a href="../node/index.html">Node landing page</a>. </p> <h3>`<iframe>` Shim</h3> <p> The MenuNav Node Plugin uses an `<iframe>` shim to prevent `<select>` elements from poking through submenus in IE 6. The `<iframe>` shim is only used for IE 6, and for performance its creation is deferred until the first time a submenu is made visible. </p> <p> Once created, the `<iframe>` shim is appended to the node representing a submenu's bounding box, and is therefore a sibling of the the a submenu's content box. All styling of the `<iframe>` is handled by the core CSS file for the MenuNav Node Plugin, so authors of custom skins won't have to worry about it. The markup template used to create each `<iframe>` is accessible via the <a href="{{apiDocs}}/classes/plugin.NodeMenuNav.html#property_NodeMenuNav.SHIM_TEMPLATE"><code>SHIM_TEMPLATE</code></a> property. </p> <p> To help users of screen readers to avoid mistakenly interacting with the `<iframe>` shim, its <code>tabindex</code> attribute is set to "-1" and its title attribute is set to "Menu Stacking Shim". The value of the `<iframe>`'s <code>title</code> attribute is available via the <a href="{{apiDocs}}/classes/plugin.NodeMenuNav.html#property_NodeMenuNav.SHIM_TEMPLATE_TITLE"><code>SHIM_TEMPLATE_TITLE</code></a> property for easy localization. Lastly, the <code>src</code> attribute of the `<iframe>` is set to "javascript:false;" so that it won't load a page inside it, preventing the secure/nonsecure warning in IE when using the MenuNav Node Plugin with HTTPS. </p> <h2>CSS reference</h2> <table> <thead> <tr> <th>Class Name</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>yui3-menu</td> <td>Applied to the element representing a menu's bounding box.</td> </tr> <tr> <td>yui3-menu-content</td> <td>Applied to the element representing a menu's content box.</td> </tr> <tr> <td>yui3-menu-hidden</td> <td>Applied to a menu's bounding box when hidden.</td> </tr> <tr> <td>yui3-shim</td> <td>Applied to the element serving as a menu's shim.</td> </tr> <tr> <td>yui3-menu-horizontal</td> <td>Renders a menu horizontally. Applied to a menu's bounding box element.</td> </tr> <tr> <td>yui3-menu-label</td> <td>Applied to the element representing a menu's label.</td> </tr> <tr> <td>yui3-menu-label-active</td> <td>Applied to a menu's label when it is a MenuNav's active descendent.</td> </tr> <tr> <td>yui3-menu-label-menuvisible</td> <td>Applied to a menu's label when its corresponding menu is visible.</td> </tr> <tr> <td>yui3-menuitem</td> <td>Applied to the element representing a menuitem's bounding box.</td> </tr> <tr> <td>yui3-menuitem-content</td> <td>Applied to the element representing a menuitem's content box.</td> </tr> <tr> <td>yui3-menuitem-active</td> <td>Applied to a menuitem when it is a MenuNav's active descendent.</td> </tr> <tr> <td>first-of-type</td> <td> Applied to the first `<ul>` element inside each menu's content box. </td> </tr> </tbody> </table> <h2>Known Issues</h2> <ul> <li><strong>Open `<select>`-based menus poke through submenus of a menu created using the MenuNav Node Plugin</strong> <p> <img src="{{componentAssets}}/select-issue.png" style="width:370px; height:257px; float:right;" alt="Screen capture of an open HTML select-based menu poking through the submenu of a menu created using the MenuNav Node Plugin"> In Safari 3 and IE 6 the `<select>` element's popup menu is modalmaking it impossible to interact with any of the other elements on the page, and therefore impossible to both trigger the display of a DHTML menu and impossible for the `<select>` element's popup menu to potentially poke through a DHTML menu. </p> <p> In all other browsers, a `<select>` element's popup menu is both <em>not</em> modal and has a zindex higher than any other element. The established best practice of using an `<iframe>` element has a shim does not fix the problem. Currently there is no fix for this issue. </p> </li> </ul>