[richfaces-issues] [JBoss JIRA] (RF-11975) Prototype script error in Portal

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on RF-11975:
----------------------------------------------

Jared MORGAN <jmorgan at redhat.com> made a comment on [bug 793999|https://bugzilla.redhat.com/show_bug.cgi?id=793999]


    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,30 +1 @@
-==MIXED RELEASE NOTE CONTENT - HANDLE KNOWN ISSUE IN ANOTHER TICKET? ==
+An issue with how PortletBridge wrapped JavaScript files from RichFaces  caused portlets to function incorrectly, and throw JavaScript errors. The fix correctly identifies the JavaScript files that require wrapping by PortletBridge using the LoadScriptStrategy ALL and WRAP_SCRIPTS true parameter values. RichFaces portlets now function correctly on Microsoft Internet Explorer and Chrome.-
-Issue 1) LoadScriptStrategy ALL does not work in all
-browsers when WRAP_SCRIPTS is true:
-
-CAUSE
-JavaScript file from RichFaces are not correctly wrapped
-CONSEQUENCE
-The portlets don't function correctly due to JavaScript errors
-FIX
-Correctly identify the JavaScript files that need to be wrapped by
-PortletBridge
-RESULT
-RichFaces portlets function correctly on IE and Chrome with LoadScriptStrategy
-ALL and WRAP_SCRIPTS true
-
-Issue 2) LoadScriptStrategy DEFAULT and ALL when WRAP_SCRIPTS true do not work
-on FF
-CAUSE
-FF seems to have a different method of recognising JavaScript functions than IE
-and Chrome
-CONSEQUENCE
-JavaScript errors saying $A() not defined for a RichFaces portlet when
-WRAP_SCRIPTS true
-FIX
-None (Fix can't be applied to PortletBridge).  It is possible to resolve it by
-moving the $A function in the JavaScript to the top of the file, but this would
-require a patch to RichFaces
-RESULT
-Known Issue - https://issues.jboss.org/browse/RF-11975
                
> Prototype script error in Portal
> --------------------------------
>
>                 Key: RF-11975
>                 URL: https://issues.jboss.org/browse/RF-11975
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 3.3.3.Final
>         Environment: GateIn v3.2
> JBoss PortletBridge v2.2.0.Final
> Firefox
>            Reporter: Ken Finnigan
>            Priority: Minor
>             Fix For: 3.Future
>
>
> When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true.  This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded.
> In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine.
> This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed.

--
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