[dojo-contributors] ContentPane calls startup on child widgets too early - is this intended?

Shane O'Sullivan shaneosullivan1 at gmail.com
Mon Oct 18 10:54:11 EDT 2010


Does anyone know who changed this, and when?  It looks like the
setContent() call on ContentPane calls dojo.parser.parse().  This
should only be done if the ContentPane has already been started, so
it's an easy fix I think.  Can the author please roll back the change?

Thanks

Shane

On 18 October 2010 05:26, Bill Keese <bill at dojotoolkit.org> wrote:
>  Doesn't sound right.   Like you said, ContentPane.startup() should
> call startup() on it's children.
>
> On 10/17/10 9:48 PM, Shane O'Sullivan wrote:
>> I noticed recently that the dojox.widget.FeedPortlet isn't working.
>> When looking to see what changed, I noticed that ContentPane, which it
>> inherits through TitlePane, calls startup() on its child widgets as it
>> parses them.
>>
>> This never happened before, and it results in startup() being called
>> on child widgets of ContentPane before startup() is called on the
>> ContentPane itself.
>>
>> Is this intended?  Surely startup() on child widgets should only be
>> called during or after startup() on the containing widget?
>>
>> Thanks
>>
>> Shane
>> _______________________________________________
>> dojo-contributors mailing list
>> dojo-contributors at mail.dojotoolkit.org
>> http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at mail.dojotoolkit.org
> http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
>


More information about the dojo-contributors mailing list