Re: [Trinidad 2] Introduce a component context stack in Trinidad to deal with visit tree calls

2010-09-27 Thread Andrew Robinson
Will change this then. The only draw back is that these APIs would not be functional for any components in trh:head and trh:html, only trh:body and children. As a result, I'll add it to trh:head as well so that, should the user use it, it will be supported there as well, so they would only be out

Re: [Trinidad 2] Introduce a component context stack in Trinidad to deal with visit tree calls

2010-09-23 Thread Matthias Wessendorf
I agree with not controlling the UIViewRoot -Matthias On Tue, Sep 21, 2010 at 12:44 PM, MAX STARETS max.star...@oracle.com wrote: Hi Andrew, I think I would rather require tr:document or trh:body (vs. tr:html) We already say in our documentation that one of these tags is required for PPR to

Re: [Trinidad 2] Introduce a component context stack in Trinidad to deal with visit tree calls

2010-09-21 Thread Andrew Robinson
Trinidad IMO should not be controlling the UIViewRoot, that is for the container to create. If we overrode it, it could also cause problems with portals. I think it best that we handle this in tr:document and trh:html as they should be the root elements of a Trinidad page. I am concerned that if

Re: [Trinidad 2] Introduce a component context stack in Trinidad to deal with visit tree calls

2010-09-21 Thread MAX STARETS
Hi Andrew, I think I would rather require tr:document or trh:body (vs. tr:html) We already say in our documentation that one of these tags is required for PPR to work. Max On 9/21/2010 3:09 PM, Andrew Robinson wrote: Trinidad IMO should not be controlling the UIViewRoot, that is for the