Opened 13 years ago

Last modified 9 years ago

#4902 closed defect

DropDownButton/ComboButton/nested Menus: memory leak on destroyRecursive() — at Version 1

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

Description (last modified by bill)

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 popup, and similarly Menu.destroy won't destroy any submenus.

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

Change History (1)

comment:1 Changed 13 years ago by bill

Description: modified (diff)
Summary: DropDowb/ComboButton, nested Menus: memory leak on destroy recursiveDropDownButton/ComboButton/nested Menus: memory leak on destroyRecursive()
Note: See TracTickets for help on using tickets.