[JBoss JIRA] Created: (RF-7520) #{rich:component('suggestion')}.callSuggestion(true) becomes practically unusable with frequency parameter on rich:suggestionbox
by Konstantin Spirov (JIRA)
#{rich:component('suggestion')}.callSuggestion(true) becomes practically unusable with frequency parameter on rich:suggestionbox
----------------------------------------------------------------------------------------------------------------------------------
Key: RF-7520
URL: https://jira.jboss.org/jira/browse/RF-7520
Project: RichFaces
Issue Type: Bug
Components: component-input
Affects Versions: 3.3.1
Environment: Any browser that can open Richfaces showcase
Reporter: Konstantin Spirov
Very simple scenario to reproduce te problem
1) Take from Richfaces showcase get RichInput:SuggestionBox:ObjectsUsageExample
2) Just add in rich:suggestionbox frequency="10" attribute
3) Recompile & redeploy
4) Click on the arrow
5) You will need to wait 10 seconds before you see the suggestion list.
Please correct the problem or create an alternative method as callSuggestionASAP()
There was a good idea behind .callSuggestion(true): to give me some solution to emulate the "combobox" - all delays after
clicking the arrow make very bad impression, they should be minimized always when if is possible.
Even without giving frequency parameter, we have default value of 400 ms. This, plus the requestDelay parameter in a4j:queue we cannot escape from,
plus the time for processing the request and... the delay before diplaying the list starts to be very visible for the end user (in local network!). We need
some practical alternative to skip at least the delay from "frequency".
--
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, 7 months
[JBoss JIRA] Created: (RF-6487) ToolTip shows old content in ajax mode.
by Alexander Dubovsky (JIRA)
ToolTip shows old content in ajax mode.
---------------------------------------
Key: RF-6487
URL: https://jira.jboss.org/jira/browse/RF-6487
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0, 3.3.1
Environment: 3.3.0.GA
3.3.1.SNAPSHOT
Reporter: Alexander Dubovsky
Assignee: Nick Belaevski
Priority: Minor
Source:
<h:outputText id="text" value="ToolTip should be here">
<rich:toolTip mode="ajax" value="#{cComp.val}"></rich:toolTip>
</h:outputText>
<br />
<a4j:commandButton action="#{cComp.action}"
value="change" />
public void action() {
val += "-add";
}
# Point on text => toolTip is shown twice: the 1th time it was empty and placed in left upper corner; the 2th time it shows correct content.
# Click "change" button and point on text again.
Result: toolTip is shown twice: the 1th time it shows old content (from step 1); the 2th time all is OK.
Time interval between two appearances is short but is visible.
--
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, 7 months
[JBoss JIRA] Created: (RF-7396) The level attribute on <richfaces:messages /> does not work properly
by Sondre Eikanger Kvalø (JIRA)
The level attribute on <richfaces:messages /> does not work properly
--------------------------------------------------------------------
Key: RF-7396
URL: https://jira.jboss.org/jira/browse/RF-7396
Project: RichFaces
Issue Type: Bug
Components: component, component-output
Affects Versions: 3.3.1
Environment: Windows XPSP3, Tomcat 6, Myfaces 1.2.7
Reporter: Sondre Eikanger Kvalø
We're trying to limit the messages rendered using the level attribute on the <rich:messages /> tag.
However, no matter what values we specify for the level attribute it renders no messages. Leaving out the attribute renders all messages.
Looking through the source we observed that the attribute value was "uppercased" before it was compared with the severity property on the message in the isApplicableMessages method in the UIRichMessages class. After comparing the value of the severity property on the message with an object from the list of severities the method returns with the statement severenities.contains(key) and this will never return true as the "key" parameter is camel case (eg: Error) while the severenities list (retrieved from the tag attribute) use upper case string values (eg: INFO, ERROR).
See comments below! :-)
protected boolean isApplicableMessage(List<String> severenities,
FacesMessage message) {
if (severenities.size() == 0 || severenities.contains("ALL")) {
return true;
}
Severity severity = message.getSeverity();
for (Object key : FacesMessage.VALUES_MAP.keySet()) {
Severity sev = (Severity) FacesMessage.VALUES_MAP.get(key);
if (0 == sev.compareTo(severity)) {
// Make the value of the "key" uppercase before invoking "contains"
return severenities.contains(key.toString().toUpperCase());
// original source
return severenities.contains(key);
}
}
return false;
}
--
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, 7 months