June 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10853) dataScroller: do not works with a4j:status properly

by Ilya Shaikovsky (JIRA)

dataScroller: do not works with a4j:status properly --------------------------------------------------- Key: RF-10853 URL: https://issues.jboss.org/browse/RF-10853 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky 1) do not works properly with form scoped default status. onstart called but onstop - not. Problem seems in dataScroller because the same case with the button works see [1] 2) do not works at all using status="status". Seems just not implemented. [1] <rich:popupPanel id="splash" autosized="true" width="200" height="80" moveable="false" resizeable="false"> <f:facet name="header"><h:outputText value="WAIT" /></f:facet> <h:outputText value="WAIT!" /> </rich:popupPanel> <h:form id="form"> <a4j:status onstart="#{rich:component('splash')}.show()" onstop="#{rich:component('splash')}.hide()" /> <h:panelGrid columnClasses="acent"> <rich:dataScroller for="table" maxPages="5" /> <rich:dataTable value="#{carsBean.allInventoryItems}" var="car" id="table" rows="#{userBean.age}"> ................ </rich:dataTable> <rich:dataScroller for="table" maxPages="5" status="status"/> </h:panelGrid> <a4j:commandButton ></a4j:commandButton> </h:form> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-10976) EDT columns cant be resized

by Lukáš Fryč (JIRA)

EDT columns cant be resized --------------------------- Key: RF-10976 URL: https://issues.jboss.org/browse/RF-10976 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Environment: RichFaces 4.1.0-SNAPSHOT r.22477 MEtamer 4.1.0-SNAPSHOT r.22479 Mojarra 2.0.4-b09 Apache Tomcat 6.0.29 OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 11.0.696.57 @ Linux i686 Firefox 4.0 Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-11048) Write QUnit tests for editor component

by Lukáš Fryč (JIRA)

Write QUnit tests for editor component -------------------------------------- Key: RF-11048 URL: https://issues.jboss.org/browse/RF-11048 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-input Reporter: Lukáš Fryč Assignee: Lukáš Fryč -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (RF-11049) Write server side unit tests for Editor

by Lukáš Fryč (JIRA)

Write server side unit tests for Editor --------------------------------------- Key: RF-11049 URL: https://issues.jboss.org/browse/RF-11049 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-input, tests - unit Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-11073) fileUpload listHeight

by ba nguyen (JIRA)

fileUpload listHeight --------------------- Key: RF-11073 URL: https://issues.jboss.org/browse/RF-11073 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Final Environment: Windows 7 Glassfish v3.1 Eclipse JEE Helios Service Release 1 FireFox 4 Reporter: ba nguyen <rich:fileUpload listHeight="1000" ... </rich:fileUpload> listHeight is ignored. No documentation regarding this feature in RichFaces 4 final releases. Referencing issue RF-9737 the fix was version 4 milestone 6. Final version does not carry on the fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (RF-10866) Queue: RF queuing rules applied to any ajax including standard f: one

by Ilya Shaikovsky (JIRA)

Queue: RF queuing rules applied to any ajax including standard f: one --------------------------------------------------------------------- Key: RF-10866 URL: https://issues.jboss.org/browse/RF-10866 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky Assignee: Nick Belaevski <a4j:queue requestDelay="1000"></a4j:queue> <h:form> <h:inputText value="#{userBean.name}"> <f:ajax event="keyup" render="out" /> </h:inputText> <h:outputText value="#{userBean.name}" id="out" /> </h:form> <a4j:log/> while typing you could see that delay applied and requests combined. could influence standard/third-party components. So need to review and probably remove. (at least make switchable) setting tran label just to review early and not for impl. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-10946) Component reference: collapsible panel contains wrong description of facets

by Pavol Pitonak (JIRA)

Component reference: collapsible panel contains wrong description of facets --------------------------------------------------------------------------- Key: RF-10946 URL: https://issues.jboss.org/browse/RF-10946 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.0.0.Final Reporter: Pavol Pitonak http://docs.jboss.org/richfaces/nightly_4_0_X/Component_Reference/en-US/h... Section "9.3.3. Appearance" in Component Reference contains wrong information about facets of rich:collapsiblePanel. Method UICollapsiblePanel.getFacetCount() return 0 so maybe this section can be removed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-10862) Autocomplete: does not perform decode of the behaviors

by Ilya Shaikovsky (JIRA)

Autocomplete: does not perform decode of the behaviors ------------------------------------------------------ Key: RF-10862 URL: https://issues.jboss.org/browse/RF-10862 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky http://community.jboss.org/message/598526#598526 checked with <rich:autocomplete mode="cachedAjax" tokens=", " minChars="0" autoFill="false" selectFirst="false" autocompleteMethod="#{autocompleteBean.autocomplete}" valueChangeListener="#{autocompleteBean.vcl}"> <a4j:ajax listener="#{autocompleteBean.list}" event="change"/> </rich:autocomplete> <h:inputText> <a4j:ajax listener="#{autocompleteBean.list}" event="change"/> </h:inputText> input calls listener and autocomplete not. Text renderer performs String clientId = decodeBehaviors(context, component); and in autocomplete there is no such code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
13
0 / 0

[JBoss JIRA] Created: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page

by Tom Giberius (JIRA)

onselectionchange working incorrect with two extendedDataTable on same page --------------------------------------------------------------------------- Key: RF-11060 URL: https://issues.jboss.org/browse/RF-11060 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Environment: GlassFish 3.0.1, Firefox Reporter: Tom Giberius Priority: Critical If you put two extendedDataTable A en B on the same page then the following goes wrong: If you selected record one of Table A en then select record one from table B then the onselectionchange trigger does not fire. The same counts for record two, three, etc. This prevents me for building a Master-Detail data entry screen where both the master and the detail are multirecord. E.g. Step 1) Select records one in master and show it details. Step 2) Select record three in details, then go back to record 3 of master and then the onselectionchange trigger does not fire. The master tables "thinks" that record three is the selected record while actually it should be record one which was the selected record in the master table. The correct behaviour should be that each table should "rember" it selected record. E.g. Step 1) Select records one in master and show it details. Step 2) Select record three in detail, then go back to record 3 of master and the onselectionchange of the master should fire so that details of master record 3 can be shown. If you would have go back to record one of the master then not firing the onselectionchange would be correct. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
14
0 / 0

[JBoss JIRA] Created: (RF-10926) Resources: add minimization for JS/CSS resources

by Nick Belaevski (JIRA)

Resources: add minimization for JS/CSS resources ------------------------------------------------ Key: RF-10926 URL: https://issues.jboss.org/browse/RF-10926 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: core Reporter: Nick Belaevski For 'production' stage we should provide minified versions of all resources as JSF does for jsf.js. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2011