Not sure this is the right Forum for this but, anyone bit by this ?

1.1 Final apparently added/finalized El.cache support for faster $.get()s; nice !

But, it breaks things like grid.destroy() when called from another Ext.on("unload") because Ext itself destroys the El.cache with it's own unload event (the first one defined, so naturally, it tears down the framework).

Which then raises the question: Is there not a global Component.destroyAll member that Ext could be calling in it's unload event before it deletes the El.cache ?

Do we even need to be concerned with obj destruction with Ext? (With non-legacy event listeners, I would imagine so.) ( Most frameworks I've contributed to/for/used track widget/component creation internally and invoke that members.destroy method on the way down.)