Bug 793999 (JBEPP-1070)
Summary: | PBR-284: rich:simpleTogglePanel does not work when placing two portlets in a page | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Masafumi Miura <mmiura> |
Component: | Portal | Assignee: | Ken Finnigan <kfinniga> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.1.0.GA | CC: | jmorgan, kfinniga, mmiura |
Target Milestone: | --- | ||
Target Release: | 5.2.1.GA | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/JBEPP-1070 | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
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 |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Masafumi Miura
2011-08-12 10:25:01 UTC
Link: Added: This issue incorporates PBR-284 Release Notes Docs Status: Added: Not Yet Documented Labels: Added: EPP_5_2_1_Candidate 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. 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 Link: Added: This issue is related to RF-11975 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 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 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 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 Michal Petrov <mpetrov> updated the status of jira RF-11975 to Closed |