February 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10170) Improve Converter finding if EL expression is semi-resolvable

by Martin Kočí (JIRA)

Improve Converter finding if EL expression is semi-resolvable ------------------------------------------------------------- Key: RF-10170 URL: https://issues.jboss.org/browse/RF-10170 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: compatibility Affects Versions: Future_4.X Environment: RichFaces 4 svn rev. 20933 Reporter: Martin Kočí example (#{bean.propertyNull} resolves to null): <h:inputText value="#{bean.propertyNull.zeitangabe}" /> outputs a input field <r:calendar value="#{bean.propertyNull.zeitangabe}" /> throws value="#{bean.propertyNull.zeitangabe}": Target Unreachable, 'propertyNull' returned null Problem is in org.richfaces.component.util.SelectUtils.findConverter: method tries to locate a Converter even if informations for this are "uknown". Simple solution can be: find converter only for ValueExpression which leads to not null value, because if no value for "value" ValueExpression :), then no conversion getAsString is necessary (at least is is true if spec does not mandates conversion for null value). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-10293) richfaces-showcase: message: not updated via ajax but h:message + outputPanel does.

by Ilya Shaikovsky (JIRA)

richfaces-showcase: message: not updated via ajax but h:message + outputPanel does. ----------------------------------------------------------------------------------- Key: RF-10293 URL: https://issues.jboss.org/browse/RF-10293 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators, examples Affects Versions: 4.0.0.Milestone5 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Nick please review "edit" sample of data table locally. (not at GAE) when you will click edit and try to enter letters in numerical fields - nothing will apears in rich:messages. So I added a4j:outputPanel and messages are appears there fine. Note: on the page with single form and out of any popups rich:message works fine. E.g. - CSV sample. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
16
0 / 0

[JBoss JIRA] Created: (RF-10367) queue: onbeforedomeupdate and ignoreDupResponce inconsistency

by Ilya Shaikovsky (JIRA)

queue: onbeforedomeupdate and ignoreDupResponce inconsistency ------------------------------------------------------------- Key: RF-10367 URL: https://issues.jboss.org/browse/RF-10367 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.Milestone5 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski check http://localhost:8080/richfaces-showcase/richfaces/component-sample.jsf?d... addUpdate() called before ignoreDupResponse check. It's problem of current demo(count of DOM updates shown same as requests count). But I believe that demo written as it should. I believe that beforedomupdate should be fired only before real DOM update. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-10397) ComponentIdResolver does not resolve id for prependId="false" correctly

by Martin Kočí (JIRA)

ComponentIdResolver does not resolve id for prependId="false" correctly ----------------------------------------------------------------------- Key: RF-10397 URL: https://issues.jboss.org/browse/RF-10397 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: base functionality Affects Versions: 4.0.0.Milestone5 Environment: Richfaces 4.0 trunk svn.rev 21378, mojarra 2.0.3 Reporter: Martin Kočí Priority: Minor <h:form id="formId" prependId="false"> <h:inputText id="inputText1" /> <h:inputText id="inputText2" > <a4j:ajax event="valueChange" execute=":formId:inputText1" /> </h:inputText> </h:form> will not execute component id="inputText1". I found that ComponentIdResolver at line 179 contains: clientId = SEPARATOR_CHAR_JOINER.join(topMatchComponent.getClientId(facesContext), id.substring(idx + 1)); But in this case topMatchComponent is HtmlForm with prependId="false" and spec says that "children of this UIForm instance in the view have the form's clientId prepended to their clientIds if and only if the form's prependId property is true". so richfaces resolve this clientId as "formId:inputText1", but it should be only "inputText1" in this case There are similar bugs registered already, but some of them are closed and some not so I can say if it is same problem. Sorry for possible duplicity. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-10426) a4j:ajax does not resolve absolute id in dataTable correctly

by Martin Kočí (JIRA)

a4j:ajax does not resolve absolute id in dataTable correctly ------------------------------------------------------------ Key: RF-10426 URL: https://issues.jboss.org/browse/RF-10426 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.Milestone5 Environment: RichFaces 4.0 trunk svn rev. 21417, mojarra 2.0.3 Reporter: Martin Kočí Priority: Critical <h:form id="f"> <h:dataTable id="t"> <h:column> <h:commandButton> <a4j:ajax render=":f:t:output"/> </h:commandButton> </h:column> <h:column > <h:outputText id="output"/> </h:column> </h:dataTable> </h:form> asdresses component with absolute search expression with ":" at start. In such case CoreRendererUtils.findComponentsFor resolvers it as "f:t:output" but that not correct because button in a iterable component. If relative search expression "f:t:output" is used or f:ajax (with absolute or relativ expression) it works fine and expression is resolved for example as "f:t:3:output" for 4th row. I marked this as critical because it prevents component targeting in complex tree, for example target a element in outer table in render="" from command button in inner table. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-9349) messages: consider inclusion of passed state functionality

by Ilya Shaikovsky (JIRA)

messages: consider inclusion of passed state functionality ----------------------------------------------------------- Key: RF-9349 URL: https://jira.jboss.org/browse/RF-9349 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component-a4j-core Reporter: Ilya Shaikovsky Assignee: Alexander Smirnov Fix For: 4.0.0.Milestone3 Alex, we had problems with that functionality in 3.3.x and turned it off(at least restricted usage at our doc resources). Need to revise that problems again and if possible - consider that feature durng development. problem details - https://jira.jboss.org/browse/RF-764 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-10447) extendedDataTable: keyboard navigation enhancements

by Ilya Shaikovsky (JIRA)

extendedDataTable: keyboard navigation enhancements --------------------------------------------------- Key: RF-10447 URL: https://issues.jboss.org/browse/RF-10447 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Milestone5 Reporter: Ilya Shaikovsky Assignee: Konstantin Mishin Fix For: 4.Next 1) I'm considering that as a bug rather than enhancement. (But not too major so including there instead of separate issue): when inner input focused - usage of arrow keys fires navigation. Does that possible to differentiate if the table is "focused", or some particular input inside? Most annoying using autocomplete or select inside 2) pageUp, pageDown, home, end keys support 3) continous scrolling while keyup/down pageUp/down hold. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-10260) rich:dropDownMenu cursor blinks/flashes through expanded menu in Internet Explorer

by Karl Mueller (JIRA)

rich:dropDownMenu cursor blinks/flashes through expanded menu in Internet Explorer ---------------------------------------------------------------------------------- Key: RF-10260 URL: https://issues.jboss.org/browse/RF-10260 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.0.0.Milestone5 Environment: Windows Vista Build 6001 apache-tomcat-7.0.5 Sun jdk1.6.0_14 RichFaces 4.0.0.20101226-M5 Mojarra JSF 2.0.3-FCS Reporter: Karl Mueller Priority: Minor Cursor blinks through expanded menu in Internet Explorer If an h:inputfield has focus and rich:dropDownMenu expands over the input field, the cursor blinks/flashes through the menu in Internet Explorer 7 & 8. This does not happen in FireFox. Adding a high z-index to the menu does not solve the issue. Unfortunately I do not have permission to add an attachment, otherwise I would have provided a screenshot. Menu (with z-index fix attempt) <rich:toolbar height="26px" style="z-index: 99999;"> <c:forEach items="#{menuBean.menuGroups}" var="menuGroup"> <rich:dropDownMenu mode="server" style="z-index: 99999;"> <f:facet name="label"> <h:outputText value="#{menuGroup.menuName}" /> </f:facet> <c:forEach items="#{menuGroup.menuElements}" var="menuElement"> <rich:menuItem style="z-index: 99999;"> <h:outputLink value="#{request.contextPath}#{menuElement.targetURL}"> <h:outputText value="#{menuElement.label}"></h:outputText> </h:outputLink> </rich:menuItem> </c:forEach> </rich:dropDownMenu> </c:forEach> </rich:toolbar> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-10248) PanelMenuItem/PanelMenuGroup: nested UIParam components should be supported

by Nick Belaevski (JIRA)

PanelMenuItem/PanelMenuGroup: nested UIParam components should be supported --------------------------------------------------------------------------- Key: RF-10248 URL: https://issues.jboss.org/browse/RF-10248 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: base functionality , component-panels-layout-themes Affects Versions: 4.0.0.CR1 Reporter: Nick Belaevski Assignee: Alex Kolonitsky Fix For: 4.0.0.CR2 Nested UIParam should be processed and sent as request parameters. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
7
0 / 0

[JBoss JIRA] Updated: (RF-10445) dataTable column header not clickable for changing sorting direction

by Oliver Freivogel (JIRA)

[ https://issues.jboss.org/browse/RF-10445?page=com.atlassian.jira.plugin.s... ] Oliver Freivogel updated RF-10445: ---------------------------------- Summary: dataTable column header not clickable for changing sorting direction (was: dataTable column header not clickable for applying sorting direction) > dataTable column header not clickable for changing sorting direction > -------------------------------------------------------------------- > > Key: RF-10445 > URL: https://issues.jboss.org/browse/RF-10445 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Milestone5 > Environment: JBoss AS 6 community edition, Apache MyFaces Tomahawk 1.10 for JSF2, Firefox 3.6.13, Safari 5.0.3, Mac OS X 10.6 > Reporter: Oliver Freivogel > > <rich:dataTable id="devices" style="margin: 10px 0px 10px 0px;" > var="device" width="100" value="#{deviceSearch.data}" sortMode="single"> > > <rich:column sortBy="#{device.type.name}" sortOrder="descending" > selfSorted="true"> > <f:facet name="header"> > <h:outputText id="deviceTypeHeaderText" > value="#{primaVista['device.type']}" /> > </f:facet> > <h:outputText value="#{device.type.name}" /> > </rich:column> > > </rich:dataTable> > Table is rendered with the correct sorting, but header is not clickable for changing the sorting direction. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2011