On 3/22/07, Simon Kitching <[EMAIL PROTECTED]> wrote:
As you say, an alternative is to walk the entire tree when the head tag is rendered (not just the children of the head) looking for components. In that case, when rendered is false for a particular node then its children can be skipped. It does feel rather odd for a component to go looking at components other than its children when rendering.
Not to run this discussion into the dirt but, it could wrap the entire body, something like: <html> <h:head> <f:facet name="otherStuffThatGoesInHead"> <h:panelGroup> <title>Look Ma, no filter!</title> <link ... /> </h:panelGroup> </f:facet> ...page body... </h:head> </html> But, I don't think there is an effective difference between the two, just semantics. The second semantics would conflict with components that want to do something similar, like Trinidad's tr:document. Or is it the depth of the looking that is odd?
