[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=12729001#comment-12729001 ] 

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

After discussions with JSF guys at Oracle today I've found out that facets within h:head are ignored if they contain h:outputStylesheet and h:outputScript elements.

The problem is that the JSF resource relocation bit finds all the outputStylesheet and outputScript elements within the head, even if they're in facets, and relocates them to be children of the head itself.  This is expected behavior as of current JSF 2 spec.  http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1139 has been raised to add the ability for facets to be added into h:head without them being ignored.
                
> 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