Changes between Initial Version and Version 1 of Ticket #9657


Ignore:
Timestamp:
Aug 5, 2009, 12:13:53 AM (12 years ago)
Author:
bill
Comment:

Hmm, that's not good. Can you attach a test case?

Maybe _Templated needs to do call startup on the nested widgets that don't have a _Container as a parent, not just top level widgets, like the parser does at the page level:

d.forEach(thelist, function(instance){
	if(	!args.noStart && instance  && 
		instance.startup &&
		!instance._started && 
		(!instance.getParent || !instance.getParent())
	){
		instance.startup();
	}
});

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9657

    • Property Owner set to bill
    • Property Milestone changed from tbd to 1.4
    • Property Summary changed from Some nested widgets in template no longer get startup() called to _Templated: some nested widgets in template no longer get startup() called
  • Ticket #9657 – Description

    initial v1  
    1 Commit 19488 changed the way that the _Templated class records its supporting widgets.
     1Commit [19488] changed the way that the _Templated class records its supporting widgets.
    22
    33Since this change, I find that when I have a template that defines widgets with nested widgets inside, the inner widgets are not getting startup() called on them.  For layout reasons, the inner widgets are sometimes not direct children of the widget's DOM node-- my understanding is that this should be allowed.