Changes between Initial Version and Version 8 of Ticket #4874


Ignore:
Timestamp:
May 26, 2008, 3:07:04 AM (13 years ago)
Author:
bill
Comment:

Dijit code might be able to use s CSS class w/!important to hide/show menu (and other widgets like Dialog), rather than setting style on the node indirectly.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4874

    • Property Status changed from new to reopened
    • Property Severity changed from major to minor
    • Property Summary changed from A Menu built programmatically does not display menu items to Menu: must hide menu with style="display: none"; indirectly via a class doesn'twork
    • Property Priority changed from high to low
    • Property Milestone changed from to 1.3

  • Ticket #4874 – Description

    initial v8  
    1 Build a menu programmatically and set contextMenuForWindow to true. Try to click on the window and the menu items do not appear.
    2 
    3 However, remove the style element display:none by commenting out the line dojo.addClass(menu.domNode, "menu1") and the MenuItems appear. So they are there, but do not display.
    4 
    5 The same code when embedded in HTML works fine (as the distro's dijit tests demonstrate).
     1If you create a menu but initially hide it via a CSS rule like:
     2{{{
     3 .menu1 {
     4      display:none;
     5}
     6}}}
     7rather than
     8{{{
     9style="display: none", then can't show it.