Opened 13 years ago

Last modified 9 years ago

#4902 closed defect

DropDowb/ComboButton, nested Menus: memory leak on destroy recursive — at Initial Version

Reported by: bill Owned by:
Priority: high Milestone: 1.1
Component: Dijit - Form Version: 0.9
Keywords: Cc:
Blocked By: Blocking:

Description

For ComboButton? or anything with a nested popup, the popup gets moved as a direct child of document.body to make positioning easier, but that means that ComboButton?.destroyRecursive() won't destroy the drop down menu, and Menu.destroy won't destroy any submenus.

This is only an issue when dynamically creating and destroying objects.

Change History (0)

Note: See TracTickets for help on using tickets.