Opened 14 years ago

Closed 14 years ago

#4826 closed defect (fixed)

allow ContentPane to hold layout container

Reported by: alex Owned by: bill
Priority: high Milestone: 1.0
Component: Dijit Version: 0.9
Keywords: contentpane, 4alex Cc: Adam Peller, Dustin Machi, Tom Trenka
Blocked By: Blocking:

Description (last modified by bill)

in many layout scenarios, ContentPane? widgets get used to stub out an area which layout widget may then occupy. Unfortunantly, ContentPanes? are black holes for resize() events, not passing them to any children, which has bit many authors of 0.9 apps pretty hard when they go to use layout-driven widgets as children of ContentPanes?.

The solution (as such) seems to be to avoid using ContentPane? widgets entirely in these cases, but I think this is naive. At a minimum, ISTM that a ContentPane? should have a mode which is "layout friendly" and passes these events down. Even if it's not the default, not forcing authors to switch out their widget hierarchy to have events passed seems preferable.

Change History (4)

comment:1 Changed 14 years ago by alex

Cc: Dustin Machi Tom Trenka added

comment:2 Changed 14 years ago by bill

Keywords: 4alex added

comment:3 Changed 14 years ago by bill

Description: modified (diff)
Status: newassigned
Summary: ContentPane widgets should have a passResize flagallow ContentPane to hold layout container

comment:4 Changed 14 years ago by bill

Resolution: fixed
Status: assignedclosed

(In [11129]) Fixes #4826: allow ContentPane? to act as a non-leaf layout container, with a single layout widget as it's child, either initially set (in this case the ContentPane? is useless and shouldn't be there) or loaded via an href.

Note: See TracTickets for help on using tickets.