A number of times we see morphedDom exception because of state changes that trigger a dom refresh on the widget after a widget is destroyed. This usually happens with unit tests. We usually get around this by setting Timeout before calling done(). But this solution is not scalable. We need to add a better check to not try re-rendering the DOM after it is destroyed.
A number of times we see morphedDom exception because of state changes that trigger a dom refresh on the widget after a widget is destroyed. This usually happens with unit tests. We usually get around this by setting Timeout before calling done(). But this solution is not scalable. We need to add a better check to not try re-rendering the DOM after it is destroyed.