Component trees which contain "unexpected" non-instantiated component material will fail on clear
Description
On discovering a subcomponent which was not instantiated by the current instantiator (and hence, by current implementation, has no path registered in it) will cause a fail in fluid.clearComponent. This manifests particularly early when, on first creation, a component makes an "unexpected component return" through use of the "returnedPath" directive interpreted by "autoInit" components.
On discovering a subcomponent which was not instantiated by the current instantiator (and hence, by current implementation, has no path registered in it) will cause a fail in fluid.clearComponent. This manifests particularly early when, on first creation, a component makes an "unexpected component return" through use of the "returnedPath" directive interpreted by "autoInit" components.