#3603 closed defect (fixed)
devise scheme for popup to tear down the widget it creates
Reported by: | Adam Peller | Owned by: | bill |
---|---|---|---|
Priority: | high | Milestone: | 0.9 |
Component: | Dijit | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
We've talked about this. Broke this out of #3580:
- Eventually we want to change Menu, TooltipDialog?? etc. so that dijit.util.popup or at least the parent widget (the DropDownButton??) closes them, rather than closing themselves, but I guess that's a separate issue.
Among the things to consider: onValueChanged, execute and cancel (might deserve their own event?)
May be related to #3462
Change History (5)
comment:1 Changed 14 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 Changed 14 years ago by
(In [9551]) Convert TooltipDialog? to issue onExecute()/onCancel() callbacks so parent knows when to close it, rather than closing itself.
Refs #3603.
comment:4 Changed 14 years ago by
comment:5 Changed 14 years ago by
Note: See
TracTickets for help on using
tickets.
(In [9550]) All widgets that popup are now required to implement either onExecute()/onCancel() or onChange() callbacks, so the parent widget knows when to close them. Think of Menu etc. as a sort of poor-man's dialog with auto-submit just by single mouse-click.
dijit.util.popup.open() changed so that it never closes the popup directly but rather notifies (via "onBlur" callback) when user has clicked something else on the screen, thereby suggesting the popup chain be closed.
dijit.util.popup.open() makes four callbacks now:
Fixes #3603. Refs #3596.