Thank you for reporting this bug. We will make it our priority to review this report.
floatingItems remain in memory after being destroyed
floatingItems remain in memory after being destroyed
The floatingItems collection is not cleared from an owning container when a window / floating component is closed and destroyed.
Fiddle:
http://ift.tt/TpixGBExt version tested:
Theme:
Browser versions tested against:- Latest FireFox
- Latest Chrome
DOCTYPE tested against:
Description:
- floatingItems are not remove from the parent container when the floating item is destroyed
Steps to reproduce the problem:
- Add a window to a panel
- Make sure the window close action is set to destroy
- Close the window
- ComponentQuery for the panel
- Check the floatingItems attribute
The result that was expected:
- The floatingItems are cleared
The result that occurs instead:
- The destroyed window is kept in memory.
Additional:
A javascript error can occur when resizing the browser window after the floating component is closedCode:
TypeError: el is null
el.addCls.apply(el, arguments);
Using fiddle, after the app has been rendered and the window closed entering the following console will show you the floating items.Code:
// i know this is disgusting
console.log(Ext.ComponentQuery.query('uxiframe')[0].getEl().select('iframe').elements[0].contentWindow.Ext.ComponentQuery.query('#mypanel')[0].floatingItems);
lundi 23 juin 2014
floatingItems remain in memory after being destroyed
Inscription à :
Publier les commentaires (Atom)
Aucun commentaire:
Enregistrer un commentaire