Opened 9 years ago
Closed 9 years ago
#14483 closed defect (invalid)
BorderContainer flow gets broken when a DropDownButton gets added with no Menu/MenuItem children
Reported by: | jonmsawyer | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | tbd |
Component: | Dijit | Version: | 1.7.1 |
Keywords: | dijit bordercontainer menu dropdownbutton button flow layout | Cc: | [email protected]… |
Blocked By: | Blocking: |
Description
For reference, see this fiddle: http://jsfiddle.net/vGqMN/7/ and attached HTML test case.
- Browser: Firefox 3.6.24, Chrome 15.0.874.106
- Platform: Ubuntu Linux 10.04 LTS (2.6.32-36-server SMP x86_64 GNU/Linux)
- Steps: Create the page as shown in http://jsfiddle.net/vGqMN/7/
- isDebug: true, parseOnLoad: true
- Declarative markup only
- Create a BorderContainer?, place a DropDownButton? in any region without any dijit children widgets and refresh the page. The flow of the BorderContainer? will break.
- Example:
<button id="menuButton" data-dojo-type="dijit.form.DropDownButton" data-dojo-props="title: 'The Menu'" > <span id="menu_image">Menu</span> <!-- Uncomment this Menu item to see correct behavior --> <!-- <span id="buttonMenu" data-dojo-type="dijit.Menu">Foo Menu</span> --> </button>
- To fix: add a dijit.Menu child element into the button
- Expected result: BorderContainer? should flow as expected with a DropDownButton? that does not have proper children
- Tested versions in which defect can be recreated: 1.6, 1.7, 1.7.1
Attachments (1)
Change History (2)
Changed 9 years ago by
Attachment: | bordercontainer-bug.html added |
---|
comment:1 Changed 9 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
This is expected; it's unsupported to create a DropDownButton without a drop down.
Note: See
TracTickets for help on using
tickets.
HTML test case in which to view defect