[JBoss JIRA] Created: (RF-7365) dropDownMenu: selectedLabelClass doesn't work if labelClass is applied
by Vadim Mikovoz (JIRA)
dropDownMenu: selectedLabelClass doesn't work if labelClass is applied
----------------------------------------------------------------------
Key: RF-7365
URL: https://jira.jboss.org/jira/browse/RF-7365
Project: RichFaces
Issue Type: Bug
Components: component-menu
Affects Versions: 3.3.2.CR1
Environment: All provided browsers
v.3.3.2-SNAPSHOT
Reporter: Vadim Mikovoz
Assignee: Nick Belaevski
Priority: Minor
Define labelClass and selectedLabelClass attributes for dropDownMenu, e.g.:
labelClass="myLabelClass", where is
.myLabelClass{
background-color: yellow;
font-style: italic;}
selectedLabelClass="mySelectedLabelClass", where is
.mySelectedLabelClass{
background-color: red;
font-style: oblique;}
1. Open test page --> labelClass is applied
2. Move mouse over menu label
--------------------------------------------
selectedLabelClass isn't applied, labelClass is applied as before
--
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
14 years, 11 months
[JBoss JIRA] Created: (RF-2393) Tree nested inside node of an outer tree has strange behaviour on ajax submit when there are validation errors
by Mike Hanafey (JIRA)
Tree nested inside node of an outer tree has strange behaviour on ajax submit when there are validation errors
--------------------------------------------------------------------------------------------------------------
Key: RF-2393
URL: http://jira.jboss.com/jira/browse/RF-2393
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4
Environment: Glassfish v2, JSF RI 1.2
Reporter: Mike Hanafey
Attachments: NestedTree.war
I have situation where there is an outer tree whose nodes have an inner tree. Specifically, the outer tree is over DNA sequences, and each DNA sequence may have a tree of comments attached to it.
Both the inner and outer trees have a couple of faces, one is used when a node is in display mode, and the other when it is in edit mode.
If the inner tree is put into edit mode at a node (via an ajax request) and a validation error occurs on a second ajax request to submit the edits, the whole inner tree for that node disappears. It can be recovered by doing a browser redisplay. If there is no validation error, the edit works as expected
Looking at the XmlHttpRequest response when there is a validation error shows that the response does not contain the expected tree nodes.
When this same comment tree code (both the backing beans and the facelets views) is applied on an unnested tree this problem does not occur.
A test war is attached (the war is big only because it includes the library dependencies -- the test code itself is small).
To demonstrate, deploy the war and look at the top page.
Click on the + next to "Comments" (this is the un-nested tree). Click "Ajax Save". Observe the "Value is required" messages.
Enter something into the first textfield, and do the "Ajax Save". Now a custom validation message appears.
Now for the first strangeness. Enter something in both the textfield and the textarea. The custom validation message appears on both inputs, but now the inputs just made are erased. When only one of these fields have data, the data entered in the other field is preserved, and I believe the clearing of input data is another error, but not the one in the title of this this issue.
To see the main issue, open the tree labeled "Sequences". This has a comments tree just like the one above nested inside the sequence node.
Click on the + next the "Comments" under "Sequences".
Click on "Ajax Save". Now instead of seeing the "Value is required" error, the inner tree node collapses. Click on the "Submit" button, an reopen the "Sequences" tree to see that the inner tree is in fact still intact.
Click on "Ajax Immediate". Now the tree does not collapse. The only difference is this button is immediate, so the validation steps are not done.
Finally, clicking on "Plain Save" shows the expected validation errors (now the Sequence tree collapses after the submit so it must be manually opened, but I guess this is expected behavior because the open / close state is not maintained across the request). The problem where the inputs that fail validation are erased remains even with this non-ajax update mode).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (RF-7356) Tooltip content is computed when submitting a form
by Anthony Ogier (JIRA)
Tooltip content is computed when submitting a form
--------------------------------------------------
Key: RF-7356
URL: https://jira.jboss.org/jira/browse/RF-7356
Project: RichFaces
Issue Type: Bug
Components: component-output
Affects Versions: 3.2.2
Environment: Windows XP / Firefox 3.0.10
Reporter: Anthony Ogier
Here is the xhtml :
----------------------------------------------------------------------------------------------------------------------------------------------------------------
<html>
<h:form>
<rich:panel>
<h:graphicImage url="/img/eye.gif"/>
<rich:toolTip followMouse="true" mode="ajax">
<f:facet name="defaultContent">
<h:outputText value="Please wait"/>
</f:facet>
<span>
<ui:repeat value="#{testBean.listLabels(4)}" var="label">
<p><h:outputText value="#{label}" /></p>
</ui:repeat>
</span>
</rich:toolTip>
</rich:panel>
<h:commandButton action="#{testBean.action}" value="Test action" />
</h:form>
</html>
----------------------------------------------------------------------------------------------------------------------------------------------------------------
and the bean :
----------------------------------------------------------------------------------------------------------------------------------------------------------------
@Name("testBean")
public class TestBean {
@Logger
private Log log;
public void action() {
log.warn("action !");
}
public String getComputedLabel() {
log.warn("getComputedLabel()");
return "computed label";
}
public List<String> listLabels(final int size) {
log.warn("listLabels("+size+")");
final ArrayList<String> list = new ArrayList<String>(size);
for (int i = 0; i < size; i++) {
list.add("Label "+(i+1));
}
return list;
}
}
----------------------------------------------------------------------------------------------------------------------------------------------------------------
When moving the mouse over the eye image, here is the server log :
11:18:25,603 WARN [bean.TestBean] listLabels(4)
11:18:25,603 WARN [bean.TestBean] listLabels(4)
The method is called twice ... but the worse is when clicking on the "Test action" button, here is the log :
11:18:33,393 WARN [bean.TestBean] listLabels(4)
11:18:33,393 WARN [bean.TestBean] action !
The content of the tooltip is computed ! That problem seems to exist only when using ui:repeat component inside the tooltip... when using c:foreach, the method listLabels is no more called at all.
I've got problem with similar usage, but with a "listLabels" method which is very long to compute, and which I don't want to be called when submitting my form.
--
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
14 years, 11 months
[JBoss JIRA] Created: (RF-5380) dropSupport: "disableDefault" attribute doesn't work.
by Mikhail Vitenkov (JIRA)
dropSupport: "disableDefault" attribute doesn't work.
-----------------------------------------------------
Key: RF-5380
URL: https://jira.jboss.org/jira/browse/RF-5380
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.BETA3)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
#1. Add dragSupport and dropSupport zones following way:
<h:panelGrid columns="1" id="panel1">
<h:panelGroup id="column1">
<a4j:outputPanel>
<rich:dragSupport dragType="dragType1"></rich:dragSupport>
<h:outputText value="Drag it 1" />
</a4j:outputPanel>
</h:panelGroup>
</h:panelGrid>
<h:panelGrid columns="1" id="panel3">
<h:panelGroup id="column3">
<a4j:outputPanel>
<rich:dropSupport acceptedTypes="dragType1"></rich:dropSupport>
<h:outputText value="Drop from 1" />
</a4j:outputPanel>
</h:panelGroup>
</h:panelGrid>
#2. For dropSupport set action="main", where "main" is action navigation to the main page, defined in faces-config.xml
#3. Set ondrop="window.open('http://www.jboss.org/','_blank','width=200,height=200');"
#4. Set disableDefault="true".
#5. Navigate to page and make drag'n'drop content from "panel1" panelGrid to "panel3" panelGrid.(acceptedTypes="dragType1")
Actual behavior:
www.jboss.org opens in new window, then "main" navigation action works.
Try to append by hands "return false;" to the ondrop handler's content and repeat Step #5 - works fine: www.jboss.org opens in new window, current page remains.
--
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
14 years, 11 months