[JBoss JIRA] Created: (RF-3350) Selection doesn't work in modalPanel with FF2
by Paul Andrews (JIRA)
Selection doesn't work in modalPanel with FF2
---------------------------------------------
Key: RF-3350
URL: http://jira.jboss.com/jira/browse/RF-3350
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5
Environment: Tomcat 5.x, MyFaces 1.1.5.
Reporter: Paul Andrews
If there is an HTML element in a modal panel that requires a selection, it doesn't work in FireFox 2.x unless you drag or resize the modal panel first. It works fine in IE6. Here is a little test page:
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<%@ taglib uri="http://richfaces.org/a4j" prefix="a4j"%>
<%@ taglib uri="http://richfaces.org/rich" prefix="rich"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title>
Modal Test
</title>
</head>
<body>
<f:view>
<rich:calendar id="date" value=""/>
<h:form>
<h:commandLink onclick="Richfaces.showModalPanel('testPanel');return false;" value="Show test panel"/>
</h:form>
<rich:modalPanel id="testPanel">
<f:facet name="header">
<h:outputText value="Test Panel" />
</f:facet>
<f:facet name="controls">
<h:graphicImage value="images/modal/close.png" style="cursor:pointer" onclick="Richfaces.hideModalPanel('testPanel')" />
</f:facet>
<h:form id="fdsdForm">
<h:commandLink onclick="Richfaces.hideModalPanel('testPanel');return false;" value="Hide this panel"/>
<h:selectOneListbox>
<f:selectItem itemValue="One"/>
<f:selectItem itemValue="Two"/>
</h:selectOneListbox>
</h:form>
</rich:modalPanel>
</f:view>
</body>
</html>
Trying to select an item in the list box doesn't work until you have dragged the page. I pored through the JavaScript source but couldn't see anything obviously wrong and all my attempts to fix the issue by simulating a drag from JavaScript failed. A work-around would be great since I get the feeling that work on the 3.1.x branch of RichFaces has ceased.
--
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
16 years, 7 months
[JBoss JIRA] Created: (RF-6138) calendar and german translation of button labels
by chris s (JIRA)
calendar and german translation of button labels
------------------------------------------------
Key: RF-6138
URL: https://jira.jboss.org/jira/browse/RF-6138
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Reporter: chris s
Priority: Trivial
Fix For: 3.3.1
Several button labels in calendar component are not translated to German:
I try to give you the best possible translation even if it's not always
the literal one:
'Apply' = 'Übernehmen'
'Today' = 'Heute'
'Clean' = 'Löschen'
'Ok' = 'OK'
'Cancel'= 'Abbrechen'
I hope you are familiar with German 'Umlaute' (öäüß, ÖÄÜ).
It's properly displayed with UTF-8 or ISO-8859-1 or -15.
If your EMail-client can't display it, here are the codes:
'Ü' in 'Übernehmen' = U+00DC or ANSI \uDC
'ö' in 'Löschen' = U+00F6 \uF6
--
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-5608) Tree : ajaxSingle doesn not keep its state if was defined via el-expression.
by Alexander Dubovsky (JIRA)
Tree : ajaxSingle doesn not keep its state if was defined via el-expression.
----------------------------------------------------------------------------
Key: RF-5608
URL: https://jira.jboss.org/jira/browse/RF-5608
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2, 3.3.0
Environment: 3.2.2.GA, 3.3.0.CR2
Reporter: Alexander Dubovsky
Assignee: Nick Belaevski
Fix For: Future
Code:
<rich:tree value="#{custom.data}" var="item">
<rich:treeNode ajaxSingle="true"
dragListener="#{item.processDrag}"
dropListener="#{item.processDrop}"
dragType="all" acceptedTypes="all">
<h:outputText value="#{item.value}" />
</rich:treeNode>
</rich:tree>
# In this case drag/drop is possible normally any node on any node => listeners are triggered OK
# Change ajaxSingle="#{true}" and try drag/srop
Result: drag/ drop operation is possible only on itself, i.e. listeners are triggered only in case drag node1 and drop it on node1 (itself).
--
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, 8 months
[JBoss JIRA] Created: (RF-7192) Ajax component processing outside of region/form
by Thomas W (JIRA)
Ajax component processing outside of region/form
------------------------------------------------
Key: RF-7192
URL: https://jira.jboss.org/jira/browse/RF-7192
Project: RichFaces
Issue Type: Bug
Components: component-a4j-core
Affects Versions: 3.3.0
Reporter: Thomas W
RF 3.3.0 GA
Issue with server side processing of AJAX enabled components that are outside of any region that is requested to be rendered as well as any a:outputPanel with ajaxRendered="true". This happens with tree and table components, for example.
I could track this down to behavior in UIDataAdapter. With the following change the unwanted processing is turned off:
public void encodeAjaxChild(FacesContext context, String path,
final Set<String> ids, final Set<String> renderedAreas) throws IOException {
boolean isRenderedPath = false;
for (String id : ids) {
if (id.startsWith(path)) {
isRenderedPath = true;
}
}
if (!isRenderedPath) {
return;
}
With this addition, any component that falls outside the list of requested ids (reRender) will be skipped. This has muted the excessive component processing (processing that would never result in DOM rendering).
A real fix would need to allow for processing of outputPanels with ajaxRendered="true". What is the correct fix for this problem?
<a:outputPanel id="searchResults" ajaxRendered="false" styleClass="noBorder">
<a:region>
<h:form id="searchForm" styleClass="noBorder">
<rich:scrollableDataTable ....
<a:support event="onselectionchange"
action="#{someAction.process}" reRender="region1,region2"
limitToList="true"
status="globalStatus"/>
--
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, 8 months