August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13019) Placeholder disappears after form reset

by Taylor Burton (JIRA)

[ https://issues.jboss.org/browse/RF-13019?page=com.atlassian.jira.plugin.s... ] Taylor Burton commented on RF-13019: ------------------------------------ We have the same issue, but I can't get mine to come back without redeploying our webserver. > Placeholder disappears after form reset > --------------------------------------- > > Key: RF-13019 > URL: https://issues.jboss.org/browse/RF-13019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.2 > Reporter: Atanu Mukherjee > Assignee: Michal Petrov > Fix For: 5.0.0.Alpha2 > > > I have the following code inside a form - > {code} > <h:inputText id="userName" styleClass="span6" > > <f:validateLength maximum="255"/> > <rich:placeholder value="ID / Username" /> > </h:inputText> > {code} > The placeholder value disappears if I reset the form. Comes back up after I click the control and tab out. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13102) rich:calendar with date pattern- input gets cleared on click

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-13102: ---------------------------------------------- Christopher O'Brien <cobrien(a)redhat.com> changed the Status of [bug 994012|https://bugzilla.redhat.com/show_bug.cgi?id=994012] from RELEASE_PENDING to CLOSED > rich:calendar with date pattern- input gets cleared on click > ------------------------------------------------------------ > > Key: RF-13102 > URL: https://issues.jboss.org/browse/RF-13102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > Assignee: Brian Leathem > Fix For: 4.3.4 > > > When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). > However, when the form is sent, the value is correctly assigned to the binded value. > Example: > {noformat} > <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> > {noformat} -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13102) rich:calendar with date pattern- input gets cleared on click

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-13102: ---------------------------------------------- Christopher O'Brien <cobrien(a)redhat.com> made a comment on [bug 994012|https://bugzilla.redhat.com/show_bug.cgi?id=994012] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > rich:calendar with date pattern- input gets cleared on click > ------------------------------------------------------------ > > Key: RF-13102 > URL: https://issues.jboss.org/browse/RF-13102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > Assignee: Brian Leathem > Fix For: 4.3.4 > > > When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). > However, when the form is sent, the value is correctly assigned to the binded value. > Example: > {noformat} > <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> > {noformat} -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-7248) a4j creates infinite HashMap.get loop

by iced guardian (JIRA)

[ https://issues.jboss.org/browse/RF-7248?page=com.atlassian.jira.plugin.sy... ] iced guardian commented on RF-7248: ----------------------------------- Why has 3.3.4.BETA1 not been included to the recent 3.3.4 Release? At least I have not been able to find the code changes suggested by Nick (thanks!) in the source code. Release notes do not exist. The workaround - manually building the jars with the help of Maven - is annoying. It is not possible for me to use Maven at work due to our company politics. (The compiled solution above is outdated.) Now I am lost. Is there no other user friendly solution? Thanks and kind regards > a4j creates infinite HashMap.get loop > ------------------------------------- > > Key: RF-7248 > URL: https://issues.jboss.org/browse/RF-7248 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 3.3.0, 3.3.3.Final > Reporter: Nida Cibulskyte > Assignee: Nick Belaevski > Labels: ENT > Fix For: 3.3.1.SP2, 3.3.4.BETA1 > > Attachments: infinite_loop.JPG, screenshot-1.jpg > > > Concurrent requests on a4j components causes infinite loop. While one request is being proccessed by restoreChildState method, another request is senT for proccessing. It causes the code to get stuck in hashmap.get() as the hashmap is not synchronized and causes infinite loop. > 2009 05 25 09:41:43 ERROR demo.NameBean - java.util.HashMap.get(HashMap.java:303) > 2009 05 25 09:41:43 ERROR demo.NameBean - org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:965) > 2009 05 25 09:41:43 ERROR demo.NameBean - org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:982) > 2009 05 25 09:41:43 ERROR demo.NameBean - org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:982) > ....................... -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13139) popupPanel duplicated if double clicking links for opening popup

by Valiantsin Shukaila (JIRA)

[ https://issues.jboss.org/browse/RF-13139?page=com.atlassian.jira.plugin.s... ] Valiantsin Shukaila commented on RF-13139: ------------------------------------------ I Didn't try it without Spring. I think this is client side issue not the server. > popupPanel duplicated if double clicking links for opening popup > ---------------------------------------------------------------- > > Key: RF-13139 > URL: https://issues.jboss.org/browse/RF-13139 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.1 > Environment: tomcat 7, Richfaces 4.3.1.Final, Spring, JSF Mojarra 2.2.0 > Reporter: Valiantsin Shukaila > Labels: popupPanel, richfaces, waiting_on_user > Attachments: RF-13139.zip > > > If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever. > I've attached zip with maven and eclipse project that can be used for reproducing the issue. > I tested on Tomcat 7.0.41. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12801: ------------------------------------ You don't want to deploy your entire app to tomcat, rather you want to deploy an as-simple-as-possible (http://sscce.org/) reproducer that re-creates the problem. As for the involved dependencies, try using the ones used by Websphere. Have a look at the server startup log to see messages indicating what versions of the involved libraries are being started. > org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Labels: ELResolver, optimization, resource, waiting_on_user, websphere > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13139) popupPanel duplicated if double clicking links for opening popup

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13139?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13139: ------------------------------------ Are you able to reproduce this behaviour without the Spring dependency? > popupPanel duplicated if double clicking links for opening popup > ---------------------------------------------------------------- > > Key: RF-13139 > URL: https://issues.jboss.org/browse/RF-13139 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.1 > Environment: tomcat 7, Richfaces 4.3.1.Final, Spring, JSF Mojarra 2.2.0 > Reporter: Valiantsin Shukaila > Labels: popupPanel, richfaces, waiting_on_user > Attachments: RF-13139.zip > > > If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever. > I've attached zip with maven and eclipse project that can be used for reproducing the issue. > I tested on Tomcat 7.0.41. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13141) rich:select item Selction not working with huge lists

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13141?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13141: ------------------------------------ The RichFaces 5 select component re-impl will likely address this issue. Follow the RF 5 javascript widget development here: https://github.com/richwidgets/richwidgets/issues/9 > rich:select item Selction not working with huge lists > ----------------------------------------------------- > > Key: RF-13141 > URL: https://issues.jboss.org/browse/RF-13141 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component, component-selects > Affects Versions: 4.3.2 > Reporter: J W > Labels: select > Fix For: 5-Tracking > > > 1) Expand the select box with a huge list > 2) Press and Hold Down Arrow-Key > 3) after a couple of seconds you can see how the marked item (the last one in the current scroll) is moving out of the visible scroll list. > 4) at this point the marked item is not visible anymore and you can not mark items anymore by hovering/using ArrowKeys. The Scroll List keeps moving whenever you move your mouse, making it actually impossible to select any item > Also: > If you scroll down in a list (20 items) move your mouse to the first partially visible item in the scroll. the scroll box will scroll up and do the same thing again since the mouse is still at the same place indicating the user wants to mark the next partially visible item. the result is,that the scroll scrolls allways 2-3 items heavily irritating the user. > I guess the __scrollToSelectedItem function in list.js is the reason for this bad behavior. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13141) rich:select item Selction not working with huge lists

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13141?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13141: ------------------------------- Fix Version/s: 5-Tracking > rich:select item Selction not working with huge lists > ----------------------------------------------------- > > Key: RF-13141 > URL: https://issues.jboss.org/browse/RF-13141 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component, component-selects > Affects Versions: 4.3.2 > Reporter: J W > Labels: select > Fix For: 5-Tracking > > > 1) Expand the select box with a huge list > 2) Press and Hold Down Arrow-Key > 3) after a couple of seconds you can see how the marked item (the last one in the current scroll) is moving out of the visible scroll list. > 4) at this point the marked item is not visible anymore and you can not mark items anymore by hovering/using ArrowKeys. The Scroll List keeps moving whenever you move your mouse, making it actually impossible to select any item > Also: > If you scroll down in a list (20 items) move your mouse to the first partially visible item in the scroll. the scroll box will scroll up and do the same thing again since the mouse is still at the same place indicating the user wants to mark the next partially visible item. the result is,that the scroll scrolls allways 2-3 items heavily irritating the user. > I guess the __scrollToSelectedItem function in list.js is the reason for this bad behavior. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13141) rich:select item Selction not working with huge lists

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13141?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13141: ------------------------------- Priority: Major (was: Critical) > rich:select item Selction not working with huge lists > ----------------------------------------------------- > > Key: RF-13141 > URL: https://issues.jboss.org/browse/RF-13141 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component, component-selects > Affects Versions: 4.3.2 > Reporter: J W > Labels: select > > 1) Expand the select box with a huge list > 2) Press and Hold Down Arrow-Key > 3) after a couple of seconds you can see how the marked item (the last one in the current scroll) is moving out of the visible scroll list. > 4) at this point the marked item is not visible anymore and you can not mark items anymore by hovering/using ArrowKeys. The Scroll List keeps moving whenever you move your mouse, making it actually impossible to select any item > Also: > If you scroll down in a list (20 items) move your mouse to the first partially visible item in the scroll. the scroll box will scroll up and do the same thing again since the mouse is still at the same place indicating the user wants to mark the next partially visible item. the result is,that the scroll scrolls allways 2-3 items heavily irritating the user. > I guess the __scrollToSelectedItem function in list.js is the reason for this bad behavior. -- 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

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2013