August 2013 - richfaces-issues - Jboss List Archives

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

by J W (JIRA)

J W created RF-13141: ------------------------ Summary: 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 Priority: Critical 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-13065) r:calendar : German translation for "Today" is "Heute"

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/RF-13065?page=com.atlassian.jira.plugin.s... ] Juergen Zimmermann closed RF-13065. ----------------------------------- Resolution: Won't Fix calendar.js contains the English labels. Internationalization has to be done via org/richfaces/renderkit/calendar_XX.properties > r:calendar : German translation for "Today" is "Heute" > ------------------------------------------------------ > > Key: RF-13065 > URL: https://issues.jboss.org/browse/RF-13065 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Fix For: 5-Tracking > > > Well, the translation of today is: Heute -- 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-8385) inputNumberSpinner: autosubmit of a form while pressing the ENTER KEY, validation is discarded and modal panel is closed

by nick humphrey (JIRA)

[ https://issues.jboss.org/browse/RF-8385?page=com.atlassian.jira.plugin.sy... ] nick humphrey commented on RF-8385: ----------------------------------- here's a quick workaround for richfaces-ui-3.3.3.Final.jar: http://nickhumphreyit.blogspot.no/2013/08/richfaces-richinputnumberspinne... this will disable form submit on enter key press inside a rich:inputNumberSpinner > inputNumberSpinner: autosubmit of a form while pressing the ENTER KEY, validation is discarded and modal panel is closed > ------------------------------------------------------------------------------------------------------------------------ > > Key: RF-8385 > URL: https://issues.jboss.org/browse/RF-8385 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 3.3.2.GA > Environment: Linux kernel 2.6.31-19 Ubuntu rel 9.10; Windows Vista/XP- Web browsers: Firefox 3.5.7; IE8 > Reporter: Eleonora Petagna > Labels: a4j_form, modalPanel, rich_inputNumberSpinner, validation > Fix For: 3.Future > > > When using an inputNumberSpinner inside a modalPanel, within an a4j:form, > pressing the Enter key will automatically submit the form and the modal panel is closed. > The validation is not performed. > I've tried to set oninputkeypress="return event.keyCode!=13" but it doesn't work. > I have also tried to catch the return-key with an additional component such as: > <rich:hotKey key="return" > like discussed in http://ahoehma.wordpress.com/tag/hotkey/ but that did not work either. > Remark: > If I replace <rich:inputNumberSpinner with <rich:inputNumberSlider the functionality is OK (the return key can be intercepted and the form is not submitted). -- 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-11469) autocomplete method does not resolve bean if ui:included

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-11469: ---------------------------- Labels: waiting_on_user (was: ) > autocomplete method does not resolve bean if ui:included > -------------------------------------------------------- > > Key: RF-11469 > URL: https://issues.jboss.org/browse/RF-11469 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Final > Reporter: u j > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include. > {code} > <ui:include src="/searchlocation.xhtml"> > <ui:param name="bean" value="#{searchBean}" /> > </ui:include> > {code} > searchlocation.xhtml contains: > {code} > <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" /> > {code} > The value binding works, but the binding in the autocompleteMethod gives: > {code} > 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null > at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11469: --------------------------------- Guys, could you please elaborate more on your sample which doesn't work, otherwise I will suppose the issue can be rejected as "Cannot reproduce". > autocomplete method does not resolve bean if ui:included > -------------------------------------------------------- > > Key: RF-11469 > URL: https://issues.jboss.org/browse/RF-11469 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Final > Reporter: u j > Assignee: Lukáš Fryč > Priority: Minor > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include. > {code} > <ui:include src="/searchlocation.xhtml"> > <ui:param name="bean" value="#{searchBean}" /> > </ui:include> > {code} > searchlocation.xhtml contains: > {code} > <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" /> > {code} > The value binding works, but the binding in the autocompleteMethod gives: > {code} > 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null > at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13052) popupPanel: @visualOptions isn't fully implemented

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13052?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13052: --------------------------------- The issue RF-13140 was created for hiding attributes. > popupPanel: @visualOptions isn't fully implemented > -------------------------------------------------- > > Key: RF-13052 > URL: https://issues.jboss.org/browse/RF-13052 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Jiří Štefek > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Setting @visualOptions doesn't work. Tried both settings from https://issues.jboss.org/browse/RF-2464 or https://issues.jboss.org/browse/RF-5239 > e.g.: 'left:1px' > OR > Is this attribute a leftover from older versions of RF (RF-3) and was replaced by attributes @*width, @*height and @style* ? > ALSO UPDATE VDL-DOC in both cases. -- 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-13140) PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13140?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13140: ---------------------------- Summary: PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet (was: PopupPanel: Hide @visualOptions and @keepVisualState options which doesn't weren't implemented yet) > PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet > ------------------------------------------------------------------------------------------ > > Key: RF-13140 > URL: https://issues.jboss.org/browse/RF-13140 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > In RF-13052 and RF-10697 we have discussed that @keepVisualState and @visualOptions attributes do not work cause they were just partiaully implemented. > Moreover, @visualOptions seems to be used just as a storage, thus it should be hidden. -- 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-10697) Popup Panel - @keepVisualState isn't fully implemented

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-10697?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-10697: --------------------------------- I have linked to RF-13140 from this issue. > Popup Panel - @keepVisualState isn't fully implemented > ------------------------------------------------------ > > Key: RF-10697 > URL: https://issues.jboss.org/browse/RF-10697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: RichFaces 4.0.0.20110227-CR1 r.21967 > Metamer 4.0.0.20110228-CR1 r.21993 > Apache MyFaces JSF-2.0 Core Impl 2.0.4 > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @Linux > Chrome 9.0.597.107 @ Linux x86_64 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Fix @keepVisualState attribute or remove it from taglib. -- 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 Sebastian Cramer (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] Sebastian Cramer commented on RF-12801: --------------------------------------- I already contacted IBM. They pointed to Richfaces. :-( Its rather hard to deploy my application to a tomcat instance. First of all I use the full EE stack in WAS8 and secondly I dont know exactly what versions of the involved dependencies (OpenJPA, OpenWebBeans, MyFaces etc) I would need to use in Tomcat to exactly reproduce the environment of WAS. Is there another way to debug this? > 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-13117) ExtendedDataTable Sorting resets $(window).resize Events

by Thomas Zuberbuehler (JIRA)

[ https://issues.jboss.org/browse/RF-13117?page=com.atlassian.jira.plugin.s... ] Thomas Zuberbuehler commented on RF-13117: ------------------------------------------ Thank you. > ExtendedDataTable Sorting resets $(window).resize Events > -------------------------------------------------------- > > Key: RF-13117 > URL: https://issues.jboss.org/browse/RF-13117 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Environment: Tomcat 7 > JBoss 7.1 > Reporter: Thomas Zuberbuehler > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Sorting removes other resize events. > At some point following code is called: > {code} > // extendedDataTable.js > deActivateResizeListener: function() { > $(window).off(this.resizeEventName); > } > {code} > Notice that this.resizeEventName is undefined. > Before code is invoked (Chrome JavaScript console) > {code} > $._data(window,'events').resize > [Object, Object] > {code} > After invoking > {code} > $._data(window,'events').resize > TypeError: Cannot read property 'resize' of undefined > {code} > http://stackoverflow.com/questions/18045891/how-to-check-if-onresize-meth... -- 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