Success! Looks like we've fixed this one. According to our records the fix was applied for
a recent build.
The issue seems to lie in the Ext.container.Monitor code, it doesn't catch that form field that is removed if it wasn't removed directly but rather by having its owner container removed.
A workaround that I'm using for now is the following. Before removing the container that contains the form fields, run:
The reason this works, btw, is because the monitor is watching for form fields being removed from their containers. It misses when a container that contains form fields is removed. But if you just remove each form field from its container first, the monitor catches that and removes the field from its list of fields that it pulls values from
Sencha Premium Member
Awesome code! Thanks @dcohn, it works!
Originally Posted by dcohn
One more question to Sencha:
@dcohn's code works without any problem. However, before I tried @dcohn's code, actually I tried the following code:
The code above works, but the container's label remained even if the container itself had been removed from the formpanel.