Opened 14 years ago

Last modified 12 years ago

#4634 closed task

MenuBar: implement — at Version 13

Reported by: bill Owned by: dante
Priority: high Milestone: 1.3
Component: Dijit Version: 0.9
Keywords: Cc: alex, nonken
Blocked By: Blocking:

Description (last modified by bill)

Implement MenuBar. Although you can get a MenuBar by using Toolbar but there are some issues with it; it doesn't quite work like menu. And it seems like a lot of people are asking for a real MenuBar. See .

From that post:

Leaving Menubar out of Dijit really feels like a mistake... It's not just a matter of using a Toolbar and DropDownButtons. That combination doesn't work the way menus work:

  1. You can't navigate left and right using arrows;
  2. you have to release the mouse button before the menu appears;
  3. the menu doesn't quite line up with the button;
  4. the overall menu structure isn't represented as such for accessibility.

Change History (13)

comment:1 Changed 14 years ago by bill

Description: modified (diff)

comment:2 Changed 14 years ago by guest

Is this still on? Would love to have it! /Max

comment:3 Changed 14 years ago by bill

Hi, still definitely planning to do it; not sure if it will make it for 1.1 though.

comment:4 Changed 13 years ago by bill

Milestone: 1.11.2

comment:5 Changed 13 years ago by dylan

Description: modified (diff)
Owner: set to dante

comment:6 Changed 13 years ago by guest

More Requirements:

1.) When clicking on a menu (say File), and then hovering over another menu (say Edit), the File menu should close and the edit should open with no additional click. The toolbar menu is "open" once one child has opened. This behavior is easily seen in the dijit.Toolbar test (with drop down buttons).

2.) Fudge factor for popup. If you click a popupmenu(submenu) and then diagonally slide your mouse, there should be a small timeout to allow you to get into the submenu without it disappearing. If you try the "history" menu in firefox, hover over "recently closed tabs" and sort of go down and to the right to get into the large list. It hangs out for a second, allowing you to get in there. Dojo menus go down unless you keep your mouse entirely in the parent menu item the whole time. This makes for a squirrely menu.

comment:7 Changed 13 years ago by bill

You've cut and paste the above comment from #6773. #1 is the main point of having a MenuBar widget, and #2 is already listed in #6773.

comment:8 Changed 13 years ago by alex

Cc: alex added

comment:9 Changed 13 years ago by nonken

Cc: nonken added

comment:10 Changed 13 years ago by dante

Milestone: 1.21.3

i've run out of 1.2 time ...

comment:11 Changed 13 years ago by dante

Priority: normalhigh
Status: newassigned

... taking a new interest in this.

comment:12 Changed 13 years ago by David Schwartz

  • Can the menu bar be used to implement a left-hand nav system?
  • Is the visual design driven entirely by .css?
  • Can the bar be oriented vertically?
  • If vertically oriented, will the menus display along the trailing edge (right side for English systems)?

comment:13 Changed 13 years ago by bill

Description: modified (diff)
Note: See TracTickets for help on using tickets.