rich:datascroller Doesnt work correctly in a portlet because of prototype.js
conflict
-------------------------------------------------------------------------------------
Key: RF-5459
URL: https://jira.jboss.org/jira/browse/RF-5459
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2, 3.3.0
Environment: JBoss Portal 2.7.0
Reporter: Muhammad Yahia
When Using rich:datascroller inside a portlet in JBoss Portal 2.7.0 and
Portlet bridge 1.0.0.B4 or 1.0.0.B5, the scroller doesnt work correctly when
the LoadStrategy for scripts is NONE, because this prevents prototype 1.6.x
from being loaded and the portal loads an old version (1.5.0). NONE strategy is
recommended by the portlet bridge to prevent multiple loading of js per portlet
(and actually some components, like TabPanel, require NONE if multiple tabpanel
portlets are on the page). I am not sure if this is an RF or portal bug, but
from a user point of view, if the bridge is used the way described in the
documentation, the datascroller will simply not work. For me I simply replaced
the portal prototype.js manually.Tested on both 3.2.2.SR1 and 3.3.0.BETA5 .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.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