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

Esmond Pitt commented on RF-7344:
---------------------------------

Done how? RichFaces 3.3.3 Final still has this behaviour.
                
> Add controls for where in the header loaded scripts are placed
> --------------------------------------------------------------
>
>                 Key: RF-7344
>                 URL: https://issues.jboss.org/browse/RF-7344
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: compatibility, core
>    Affects Versions: 3.3.1
>         Environment: IE8
>            Reporter: Jay Balunas
>            Assignee: Nick Belaevski
>             Fix For: 3.3.2.CR1
>
>          Time Spent: 1 day
>  Remaining Estimate: 0 minutes
>
> IE8 requires some header content be located at the very top of the header.  
> Because RichFaces places some of the loaded scripts first this can break.
> For example "<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />" 
> will be ignored if not the first element after the header.  Although the work 
> around can be to just place the value in the header directly "<header 
> name="X-UA-Compatible">IE=EmulateIE7</header>", RichFaces should have a way 
> to control the location of the scripts in the header.
> This could take the form of a new context param or perhaps a tag that RF can 
> trigger off of for default script placement.  If not there behavior is 
> defaulted to current.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to