Changes between Initial Version and Version 1 of Ticket #4902


Ignore:
Timestamp:
Oct 27, 2007, 7:10:42 AM (13 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4902

    • Property Summary changed from DropDowb/ComboButton, nested Menus: memory leak on destroy recursive to DropDownButton/ComboButton/nested Menus: memory leak on destroyRecursive()
  • Ticket #4902 – Description

    initial v1  
    1 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.
     1For 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.
    22
    33This is only an issue when dynamically creating and destroying objects.