Ticket #4634 (assigned task)

Opened 14 months ago

Last modified 11 days ago

MenuBar: implement

Reported by: bill Owned by: dante
Priority: high Milestone: 1.4
Component: Dijit Version: 0.9
Severity: normal Keywords:
Cc: alex, nonken

Description (last modified by bill) (diff)

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 http://dojotoolkit.org/forum/support/dijit/menubar .

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

Changed 14 months ago by bill

  • description modified (diff)

Changed 12 months ago by guest

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

Changed 12 months ago by bill

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

Changed 11 months ago by bill

  • milestone changed from 1.1 to 1.2

Changed 7 months ago by dylan

  • owner set to dante
  • description modified (diff)

Changed 6 months 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.

Changed 6 months 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.

Changed 6 months ago by alex

  • cc alex added

Changed 6 months ago by nonken

  • cc nonken added

Changed 5 months ago by dante

  • milestone changed from 1.2 to 1.3

i've run out of 1.2 time ...

Changed 4 months ago by dante

  • priority changed from normal to high
  • status changed from new to assigned

... taking a new interest in this.

Changed 3 months ago by drschwartz

  • 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)?

Changed 3 months ago by bill

  • description modified (diff)

Changed 11 days ago by bill

  • milestone changed from 1.3 to 1.4

bumping 1.4 tickets to 1.5, and most 1.3 tickets to 1.4

Note: See TracTickets for help on using tickets.