Bug 793999 (JBEPP-1070) - PBR-284: rich:simpleTogglePanel does not work when placing two portlets in a page
Summary: PBR-284: rich:simpleTogglePanel does not work when placing two portlets in a ...
Keywords:
Status: CLOSED DEFERRED
Alias: JBEPP-1070
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.1.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.1.GA
Assignee: Ken Finnigan
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-12 10:25 UTC by Masafumi Miura
Modified: 2015-03-09 14:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
EPP 5.1.0, RIchfaces 3.3.1.SP2 and Portlet Bridge 2.1.0.GA.EPP51
Last Closed: 2012-02-10 03:05:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1070 0 Major Closed PBR-284: rich:simpleTogglePanel does not work when placing two portlets in a page 2018-10-18 12:02:55 UTC
Red Hat Issue Tracker RF-11975 0 Minor Closed Prototype script error in Portal 2018-10-18 12:02:55 UTC

Description Masafumi Miura 2011-08-12 10:25:01 UTC
Affects: Release Notes
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000007qCHg
project_key: JBEPP

Platform JIRA for PBR-284

Comment 1 Masafumi Miura 2011-08-12 10:32:57 UTC
Link: Added: This issue incorporates PBR-284


Comment 3 Jared MORGAN 2011-11-16 03:55:02 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 4 hfnukal@redhat.com 2012-01-13 11:46:05 UTC
Labels: Added: EPP_5_2_1_Candidate


Comment 6 Ken Finnigan 2012-02-10 03:05:12 UTC
Was able to resolve the problem of IE and Chrome not working with LoadScriptStrategy set to ALL and WRAP_SCRIPTS true.  However, the only way to allow the portlets to function correctly within FF is to modify the prototype.js and framework_pack.js files to move the $A JS function to the top of the file, otherwise FF believes the function is not defined.

Comment 7 Ken Finnigan 2012-02-10 03:05:12 UTC
Labels: Removed: EPP_5_2_1_Candidate 
Release Notes Text: Added: 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


Comment 8 Ken Finnigan 2012-02-10 13:57:38 UTC
Link: Added: This issue is related to RF-11975


Comment 9 Jared MORGAN 2012-03-26 04:37:25 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
==MIXED RELEASE NOTE CONTENT - HANDLE KNOWN ISSUE IN ANOTHER TICKET? ==

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

Comment 10 Ken Finnigan 2012-03-26 14:03:30 UTC
I guess a new ticket could be opened, but I don't believe it's an issue that will ever be resolved.

Best person to ask is Thomas about what he wants

Comment 11 Ken Finnigan 2012-03-26 14:03:30 UTC
    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:
@@ -27,4 +27,4 @@
 moving the $A function in the JavaScript to the top of the file, but this would
 require a patch to RichFaces
 RESULT
-Known Issue+Known Issue - https://issues.jboss.org/browse/RF-11975

Comment 12 Jared MORGAN 2012-04-11 03:16:09 UTC
    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

Comment 13 JBoss JIRA Server 2015-03-09 14:46:53 UTC
Michal Petrov <mpetrov> updated the status of jira RF-11975 to Closed


Note You need to log in before you can comment on or make changes to this bug.