February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12771) Rich:tabPanel - Regression ? Behavior has been changed on getting ID via itemChangeListener

by Jean ANDRE (JIRA)

[ https://issues.jboss.org/browse/RF-12771?page=com.atlassian.jira.plugin.s... ] Jean ANDRE updated RF-12771: ---------------------------- Summary: Rich:tabPanel - Regression ? Behavior has been changed on getting ID via itemChangeListener (was: Rich:tabPanel - Regression ? Behavior has been change on getting ID via itemChangeListener) > Rich:tabPanel - Regression ? Behavior has been changed on getting ID via itemChangeListener > ------------------------------------------------------------------------------------------- > > Key: RF-12771 > URL: https://issues.jboss.org/browse/RF-12771 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Environment: Tested on GlassFish - Mojarra 2.1.17 - Indigo on our ITHB (Integration Technologies Bug Hunter) > Reporter: Jean ANDRE > > In version 4.2.3, under mojarra 2.1.17, we can get the active tab through the listener and the event ItemChangeEvent. This object contains the new and the old tab id without the fully qualified id of the tab, just the id we gave to the tab in our XHTML. ex: TAB_CLIENT-01-1. > But in version 4.3.0.Final, same JSF implementation, we got a fully qualified ID: ex desktopForm:TAB_CLIENT-01-1. > That breaks the application because, now, we have to take care about the fully qualified name instead having a simple one. This implementation is less transparent and is not compatible with the previous version. > Is it a regression ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12773) orderingList/pickList - Firefox renders buttons too narrow if the list is too wide

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-12773?page=com.atlassian.jira.plugin.s... ] Michal Petrov updated RF-12773: ------------------------------- Attachment: list.png > orderingList/pickList - Firefox renders buttons too narrow if the list is too wide > ---------------------------------------------------------------------------------- > > Key: RF-12773 > URL: https://issues.jboss.org/browse/RF-12773 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.0.CR2 > Environment: Firefox 18.0 > Reporter: Michal Petrov > Attachments: list.png > > > When the width of div.rf-ord-lst-scrl is set too wide (wider than the parent element) the control buttons are narrowed to a minimum ignoring the text inside them. > Can be reproduced from console, at http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=orderin... set the div width to 500px > There is no issue in Chrome or Opera. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12773) orderingList/pickList - Firefox renders buttons too narrow if the list is too wide

by Michal Petrov (JIRA)

Michal Petrov created RF-12773: ---------------------------------- Summary: orderingList/pickList - Firefox renders buttons too narrow if the list is too wide Key: RF-12773 URL: https://issues.jboss.org/browse/RF-12773 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 4.3.0.CR2 Environment: Firefox 18.0 Reporter: Michal Petrov When the width of div.rf-ord-lst-scrl is set too wide (wider than the parent element) the control buttons are narrowed to a minimum ignoring the text inside them. Can be reproduced from console, at http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=orderin... set the div width to 500px There is no issue in Chrome or Opera. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12772) rich:fileUpload does not working properly (style, script)

by Byambaa MD (JIRA)

[ https://issues.jboss.org/browse/RF-12772?page=com.atlassian.jira.plugin.s... ] Byambaa MD updated RF-12772: ---------------------------- Summary: rich:fileUpload does not working properly (style, script) (was: rich:fileUpload does not working properly when CONTEXT-PARAM (org.richfaces.SKIN)) Environment: when CONTEXT-PARAM (org.richfaces.SKIN=none and org.richfaces.CONTROL_SKINNING=disable and org.richfaces.CONTROL_SKINNING_CLASSES=disable and org.richfaces.enableControlSkinning=false and org.richfaces.LoadStyleStrategy=NONE and org.richfaces.LoadScriptStrategy=NONE) Description: rich:fileUpload does not working properly and require need to refresh browser when ... > rich:fileUpload does not working properly (style, script) > --------------------------------------------------------- > > Key: RF-12772 > URL: https://issues.jboss.org/browse/RF-12772 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: when CONTEXT-PARAM (org.richfaces.SKIN=none and org.richfaces.CONTROL_SKINNING=disable and org.richfaces.CONTROL_SKINNING_CLASSES=disable and org.richfaces.enableControlSkinning=false and org.richfaces.LoadStyleStrategy=NONE and org.richfaces.LoadScriptStrategy=NONE) > Reporter: Byambaa MD > > rich:fileUpload does not working properly and require need to refresh browser when ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12772) rich:fileUpload does not working properly when CONTEXT-PARAM (org.richfaces.SKIN)

by Byambaa MD (JIRA)

Byambaa MD created RF-12772: ------------------------------- Summary: rich:fileUpload does not working properly when CONTEXT-PARAM (org.richfaces.SKIN) Key: RF-12772 URL: https://issues.jboss.org/browse/RF-12772 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Byambaa MD -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12771) Rich:tabPanel - Regression ? Behavior has been change on getting ID via itemChangeListener

by Jean ANDRE (JIRA)

[ https://issues.jboss.org/browse/RF-12771?page=com.atlassian.jira.plugin.s... ] Jean ANDRE updated RF-12771: ---------------------------- Summary: Rich:tabPanel - Regression ? Behavior has been change on getting ID via itemChangeListener (was: Rich:tabPanel - Regression ? Behavior has been change on geting ID via itemChangeListener) > Rich:tabPanel - Regression ? Behavior has been change on getting ID via itemChangeListener > ------------------------------------------------------------------------------------------ > > Key: RF-12771 > URL: https://issues.jboss.org/browse/RF-12771 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Environment: Tested on GlassFish - Mojarra 2.1.17 - Indigo on our ITHB (Integration Technologies Bug Hunter) > Reporter: Jean ANDRE > > In version 4.2.3, under mojarra 2.1.17, we can get the active tab through the listener and the event ItemChangeEvent. This object contains the new and the old tab id without the fully qualified id of the tab, just the id we gave to the tab in our XHTML. ex: TAB_CLIENT-01-1. > But in version 4.3.0.Final, same JSF implementation, we got a fully qualified ID: ex desktopForm:TAB_CLIENT-01-1. > That breaks the application because, now, we have to take care about the fully qualified name instead having a simple one. This implementation is less transparent and is not compatible with the previous version. > Is it a regression ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12771) Rich:tabPanel - Regression ? Behavior has been change on geting ID via itemChangeListener

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12771: ------------------------------- Summary: Rich:tabPanel - Regression ? Behavior has been change on geting ID via itemChangeListener Key: RF-12771 URL: https://issues.jboss.org/browse/RF-12771 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.Final Environment: Tested on GlassFish - Mojarra 2.1.17 - Indigo on our ITHB (Integration Technologies Bug Hunter) Reporter: Jean ANDRE In version 4.2.3, under mojarra 2.1.17, we can get the active tab through the listener and the event ItemChangeEvent. This object contains the new and the old tab id without the fully qualified id of the tab, just the id we gave to the tab in our XHTML. ex: TAB_CLIENT-01-1. But in version 4.3.0.Final, same JSF implementation, we got a fully qualified ID: ex desktopForm:TAB_CLIENT-01-1. That breaks the application because, now, we have to take care about the fully qualified name instead having a simple one. This implementation is less transparent and is not compatible with the previous version. Is it a regression ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12770) rich:select not work properly after filtering list

by Cristiano Moraes (JIRA)

Cristiano Moraes created RF-12770: ------------------------------------- Summary: rich:select not work properly after filtering list Key: RF-12770 URL: https://issues.jboss.org/browse/RF-12770 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.3.0.M3, 4.3.0.Final Environment: Win7. Firefox 18, Chrome 24 and IE9. MyFaces 2.1.8. Tomcat 6.0.35 Reporter: Cristiano Moraes With enableManualInput parameter as "true" if I typed some caracters in the field, and then I try to click at any option but the first in the filtered list, component always pick the first. How reproduce it: It is happing at showcase. Choose rich:select option at menu. At "Select with manual input" field, type 'al'. Alabama and Alaska will show up in the list. Try click in Alaska (second option), Alabama will be select. The same happens if you filter the list and select the option using arrows keys and press tab. Otherwise, it will work if you do that but press Enter in the end. Change selectFirst parameter value has no effect. It works in 4.3.0.M1 release. Sorry bad english mistakes. If I was not clear, ask me to clarify. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12762) Duplicate id problem in ExtendedDatatable with dynamic columns

by Christophe Noel (JIRA)

[ https://issues.jboss.org/browse/RF-12762?page=com.atlassian.jira.plugin.s... ] Christophe Noel commented on RF-12762: -------------------------------------- I don't know if it is caused by the same problem, but the columns are unsortable (using c:forEach). Environment: Liferay 6.0.5 on Tomcat6, Liferay FAces Bridge 3.0.1 GA2 > Duplicate id problem in ExtendedDatatable with dynamic columns > -------------------------------------------------------------- > > Key: RF-12762 > URL: https://issues.jboss.org/browse/RF-12762 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR1 > Environment: Windows 7 , weblogic10.4.3, Myfaces 2.1.10, IE 9, FireFox 14.0.1 > Reporter: blam lam > Priority: Critical > Fix For: 5-Tracking > > > When the ExtendedDataTable contains dynamic columns (i.e. using for:each), "java.lang.IllegalStateException: component with duplicate id" will occur after the second submit from a commandButton. > The problem does not appear in 4.2.3 Final but found in 4.3 CR1 > Sample source code: > {code} > <h:form id="frmMarkUpdate"> > <a4j:outputPanel id="resultPanel"> > <rich:extendedDataTable id="studentVoMarkInputTab" > value="#{updateMarkBean.studentVoMarkAmends}" > var="studVo" > selectionMode="none" > height="100%"> > > <rich:column width="200px" > > <f:facet name="header"> > Status > </f:facet> > <h:outputText value="#{studVo.student.markAmendStatus}" /> > </rich:column> > > <c:forEach items="#{updateMarkBean.taskVos}" var="tvo" varStatus="s"> > <rich:column width="100px"> > <f:facet name="header"> > <h:outputText value="#{tvo.task.taskName}" /> > </f:facet> > <h:inputText id="task#{s.index}_amk" > value="#{studVo.getTaskMarkMap().get(tvo.task.taskId).amendedMark}" > size="1" maxlength="3"/> > </rich:column> > </c:forEach> > </rich:extendedDataTable> > > <a4j:commandButton id="btnSave" value="Save" > action="#{updateMarkBean.doBeforeSave}" > styleClass="button blue"> > </a4j:commandButton> > > </a4j:outputPanel> > </h:form> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12769) Select Component with Manual Input uses first option regardless of what is picked

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/RF-12769?page=com.atlassian.jira.plugin.s... ] Cody Lerum commented on RF-12769: --------------------------------- Also the selectitem event isn't fired on the first click. If you were to click Nebraska from the drop down (which now only includes Nebraska) the event will be fired. > Select Component with Manual Input uses first option regardless of what is picked > --------------------------------------------------------------------------------- > > Key: RF-12769 > URL: https://issues.jboss.org/browse/RF-12769 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Cody Lerum > Labels: regression > > Visible on showcase. > Got to select component with manual input. Type "n" then select "New Jersey" > Nebraska will be selected instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 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 2013