[richfaces-issues] [JBoss JIRA] (RF-12537) Resource Ordering -aware HeadRenderer

[Ken Finnigan (JIRA)]

    [ https://issues.jboss.org/browse/RF-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729410#comment-12729410 ] 

Ken Finnigan commented on RF-12537:
-----------------------------------

Lukas, unfortunately it goes beyond that.

I had my own head renderer and would see no facets inside encodeEnd() of that renderer if the facets just had outputScript or outputStylesheet elements present.

The JSF resource relocation, which supports targeting resources at the head of page from inside the body, is the bit that "relocates" the outputScript and outputStylesheet elements from inside the facet to directly on the view root.  And as there is nothing else in the facet the facet is no longer there.

If you have other tags in the facet other than outputScript and outputStylesheet, the facet is present with only those non JS/CSS tags.

>From what I understand, if you link to JS/CSS with just the plain html <link>, then those links are not relocated by JSF and the facets would be present.
                
> Resource Ordering -aware HeadRenderer
> -------------------------------------
>
>                 Key: RF-12537
>                 URL: https://issues.jboss.org/browse/RF-12537
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: core
>            Reporter: Lukáš Fryč
>             Fix For: 5-Tracking
>
>
> The order of resources rendered in a head is currently un-managed and can cause resource ordering issues. (Which may be partially fixed by using different placement of h:outputScript tags).
> Furthermore a performance of application perceived by user might be significantly enhanced when ordering head resources correctly (see Yahoo recommendations).
> The proposal of {{HeadRenderer}} by Adrian Mitev:
> https://gist.github.com/3899465
> ----
> This proposal has several drawbacks:
> * doesn't count with mime-types, depends on resource names (Resource provided by ResourceHandler may be used here to obtain mime-type)
> * resource names stored in attribute "name" are not part of JSF spec (afaik) and thus implementation-dependent
> * the implementation does not count with resource library notion (.reslib)
> * ECSS is unsupported, but it can be simply changed with using ResourceHandler as described above
> Other than that the proposed solution seems like enough generic.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira