[JBoss JIRA] Created: (RF-7016) <rich:jQuery> usage example with <h:graphicImage>, uses conflicting mouseOver handlers.
by Scott Langley (JIRA)
<rich:jQuery> usage example with <h:graphicImage>, uses conflicting mouseOver handlers.
---------------------------------------------------------------------------------------
Key: RF-7016
URL: https://jira.jboss.org/jira/browse/RF-7016
Project: RichFaces
Issue Type: Bug
Components: doc
Affects Versions: 3.3.0
Reporter: Scott Langley
Priority: Minor
In the RichFaces Reference Guide, in the section 6.66.5. Details of Usage for the <rich:jQuery> component, one suggested usage is:
...
<h:graphicImage onmouseover="enlargePic(this)" width="50" value="/images/price.png"
onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseover="releasePic(this)" />
<h:graphicImage onmouseover="enlargePic(this)" width="50" value="/images/discount.png"
onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseover="releasePic(this)" />
...
<rich:jQuery name="enlargePic" timing="onJScall" query="animate({width:param.pwidth})" />
<rich:jQuery name="releasePic" timing="onJScall" query="animate({width:'50px'})"/>
...
If you try to run something resembling this, you get errors like:
Attribute "onmouseover" was already specified for element "h:graphicImage".
because they are assigning three times to the 'onmouseover' handler function. I assume that the author meant to use this code:
...
<h:graphicImage width="50" value="/images/price.png"
onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this)" />
<h:graphicImage width="50" value="/images/discount.png"
onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this)" />
--
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
16 years, 10 months
[JBoss JIRA] Created: (RF-7250) Tree node labels becoming blank after doing a lot of expansion/collapsing. Occurs at random
by teena george (JIRA)
Tree node labels becoming blank after doing a lot of expansion/collapsing. Occurs at random
-------------------------------------------------------------------------------------------
Key: RF-7250
URL: https://jira.jboss.org/jira/browse/RF-7250
Project: RichFaces
Issue Type: Bug
Components: JSF 2.0
Affects Versions: 3.3.1
Environment: Windows XP, IE7
Reporter: teena george
Hi,
I am using a tree component in my project. When I expand or collapse the tree nodes, the tree node names vanishes at random intervals. This does not happen always. It occurs after I do a lot of expansion/ collapsing of the various tree nodes. If I refresh the page everything comes back to normal and the tree is perfect. Even when the tree misses the labels, the tree functions properly.
I tested my tree component in RichFaces 3.3.1 and this issue is still there. I had another problem when I was using RichFaces 3.2.2.. The labels names change to an Object.ToString() format.. As an example, if my node label is to come from the 'name' property of the object 'TestObject' the label name would change to 'TestObject@23534569' at random intervals. As far as I tested this issue is removed in 3.3.1.
Please provide some light on this if any of you have come across the same issue.
Regards,
Teena
--
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
16 years, 10 months
[JBoss JIRA] Created: (RF-6338) PanelMenu does not work in 3.3.1.SNAPSHOT
by Alexander Dubovsky (JIRA)
PanelMenu does not work in 3.3.1.SNAPSHOT
-----------------------------------------
Key: RF-6338
URL: https://jira.jboss.org/jira/browse/RF-6338
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.1
Environment: 3.3.1.SNAPSHOT
Reporter: Alexander Dubovsky
Assignee: Nick Belaevski
Priority: Critical
Source:
<h:form>
<rich:panelMenu>
<rich:panelMenuGroup label="group 1">
<rich:panelMenuItem label="it 1.1" action="#{cComp.test}" />
<rich:panelMenuItem label="it 1.2" action="#{cComp.test}" />
<rich:panelMenuItem label="it 1.3" action="#{cComp.test}" />
</rich:panelMenuGroup>
<rich:panelMenuGroup label="group 2">
<rich:panelMenuItem label="it 2.1" action="#{cComp.test}" />
<rich:panelMenuItem label="it 2.2" action="#{cComp.test}" />
<rich:panelMenuItem label="it 2.3" action="#{cComp.test}" />
</rich:panelMenuGroup>
</rich:panelMenu>
</h:form>
Menu is not expanded/collapsed.
The same code was working well in 3.3.0.GA
--
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
16 years, 10 months
[JBoss JIRA] Created: (RF-6620) rich:orderingList does not update model with newly ordered list
by Scott Farley (JIRA)
rich:orderingList does not update model with newly ordered list
---------------------------------------------------------------
Key: RF-6620
URL: https://jira.jboss.org/jira/browse/RF-6620
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0, 3.2.1
Environment: RichFaces 3.3.0 GA on JSF 1.2 (SUN RI) with Facelets.
Reporter: Scott Farley
When using <rich:orderingList> on a simple facelets page the the model object is not updated with the newly ordered list. I can see this work with RichFaces 3.1.3 but NOT 3.2.1 or 3.3.0. My scenario includes using a JSF managed bean with a value of List<MyDataType> which is referenced in the "value" attribute of the "rich:orderingList" element. The model setter method does get called on the managed bean when a commandButton fires an action but the model still has the original list. Also the value changed event is not fired.
Debugging the code showed that only in version 3.1.3 did the UIOderingList.validate(FacesContext context) method "walk" over the newly submitted values to build a list with the new values. Version 3.3.0 walks over the original values instead causing the newValue to be the old value but still calls the setSelection() and setActiveItem() allowing them to work correctly.
--
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
16 years, 10 months