#3042 closed defect (fixed)
[PopupManager] onMouse prevents popup from closing
Reported by: | haysmark | Owned by: | bill |
---|---|---|---|
Priority: | high | Milestone: | 0.9beta |
Component: | Dijit | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
onMouse incorrectly calls stack[0].close; it should call dijit.util.PopupManager?.close(true).
The effect of this defect is that popups cannot close unless they provide code that hides themselves, which PopupManager?.close already provides, and is supposed to provide.
Getting this to work will be important for migrating AutoCompleter? to use PopupManager? entirely.
Change History (4)
comment:1 Changed 14 years ago by
Status: | new → assigned |
---|
comment:2 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [8656]) Fix PopupManager? so that it doesn't depend on popup implementing a close() function, thus allowing any widget to be popped-up (as per the original design goal). Fixes #3042 but need some more work on Menu; I want to move code from MenuItem? up into Menu.
comment:3 Changed 14 years ago by
comment:4 Changed 14 years ago by
Note: See
TracTickets for help on using
tickets.
Ah you are right. PopupManager? shouldn't require an close() function on the widget. We do need an (optional) onClose() callback though, to tell popups when they are closing because in Menu's case it needs to do some cleanup. I will fix.