January 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8240) Header row of extended data table out of synch with data rows beneath after resizing browser

by hase hase (JIRA)

Header row of extended data table out of synch with data rows beneath after resizing browser -------------------------------------------------------------------------------------------- Key: RF-8240 URL: https://jira.jboss.org/jira/browse/RF-8240 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 3.3.1 Environment: IE7, IE8, FF3.0. FF3.5 Reporter: hase hase <rich:extendedDataTable width="100%"> if this is used in an container with a "widht XXX%", then the header row of the extended Data Table get out of sync with the data rows beneath, when the browser window is scaled from full screen to window mode (vice versa, too). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-8213) rf-demo (JSF2): Validators don't work (AS 6.0.0.M1)

by Lukas Fryc (JIRA)

rf-demo (JSF2): Validators don't work (AS 6.0.0.M1) --------------------------------------------------- Key: RF-8213 URL: https://jira.jboss.org/jira/browse/RF-8213 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF 2.0 Affects Versions: 3.3.3.BETA1 Environment: JBoss AS 6.0.0.M1 JDK 1.6.0_16 Firefox 3.5.5 richfaces-demo-jsf2-3.3.3-20091205.161803-10.war Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 3.3.3.CR1 Validators are broken in richfaces-demo-jsf2 with AS 6.0.0.M1. It doesn't validate at all (with exception of integer-only validation) Results from http://hudson.qa.jboss.com/hudson/view/RichFaces/job/richfaces-3.3-JSF2-d... verified manually. (Attached screenshots of results) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
17
0 / 0

[JBoss JIRA] Created: (RF-8229) ExtendedDataTable: programmatic changes in table state are not reflected visually

by Nick Belaevski (JIRA)

ExtendedDataTable: programmatic changes in table state are not reflected visually ---------------------------------------------------------------------------------- Key: RF-8229 URL: https://jira.jboss.org/jira/browse/RF-8229 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nick Belaevski Use case description: add new column to the rich:extendedDataTable and make it the first one. Tried this: public void addColumn() throws Exception { UIExtendedDataTable table =(UIExtendedDataTable) component; HtmlColumn column = new HtmlColumn(); column.setId("dynamicColumn"); column.getChildren().add(new HtmlOutputText()); table.getChildren().add(0, column); } but columns is always added the second, because rich:extendedDataTable maintains list of columns and sorting it accordingly. New column is just missing there after addition. Tried to bind "tableState" to the bean, but it's not read. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (RF-2490) Header facet in the rich:dataTable ignore column "rendered" attribute

by Alexander Smirnov (JIRA)

Header facet in the rich:dataTable ignore column "rendered" attribute --------------------------------------------------------------------- Key: RF-2490 URL: http://jira.jboss.com/jira/browse/RF-2490 Project: RichFaces Issue Type: Bug Environment: RichFaces 3.2 snapshot from 3/10. Reporter: Alexander Smirnov Assigned To: Alexander Smirnov Fix For: 3.2.0 The headers of data tables are no longer following the render rule of its parent h:column tag. The headers are rendering no matter what the rule is. The actual content is following the render rule. I noticed that if I wrap the whole h:column into an a4j:region tag and place the render rule there instead, it all renders correctly. However, I think it should work the way it was before right ?? The f:facet tag should comply to the render rule in the h:column tag ? Here's a code snippet....... <rich:dataTable ...> <h:column id="checkBoxCol" rendered="#{itemList_editableUser or itemList_subProfileView or itemList_DownloadableUser}"> <f:facet name="header"> <h:selectBooleanCheckbox styleClass="checkbox" immediate="true" id="headerCheckBox" onclick="toggleElementCheckboxes(this, this.checked)"/> </f:facet> <h:selectBooleanCheckbox value="#{item.selected}" title="#{item.object.itemIdentifier.gtin}" styleClass="checkbox" id="rowCheckBox" disabled="#{(itemList_subProfileView and itemList_subProfRestr) or item.acctAccess == 'N'}"/> </h:column> ........ </rich:dataTable> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

8
13
0 / 0

[JBoss JIRA] Created: (RF-8241) last a4j:commandButton in a ui:repeat does not rerender component after action

by Andreas Schank (JIRA)

last a4j:commandButton in a ui:repeat does not rerender component after action ------------------------------------------------------------------------------ Key: RF-8241 URL: https://jira.jboss.org/jira/browse/RF-8241 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 3.3.2.SR1 Reporter: Andreas Schank The last a4j:commandButton in a ui:repeat does not rerender after the action, other a4j:commandButtons further ahead do. The action method is called. When replacing ui:repeat with a4j:repeat everything works fine. a4jCommandButton is defined as follows: <a4j:commandButton value="-" action="#{basicProfileBean.actionRemoveEmail}" reRender="email_table"> <a4j:actionparam name="index" value="#{email.index}" assignTo="#{basicProfileBean.selectedEmailIndex}" /> </a4j:commandButton> (email_table is a panel group outside the ui:repeat) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-8248) model dialog framework

by Dave Chen (JIRA)

model dialog framework ---------------------- Key: RF-8248 URL: https://jira.jboss.org/jira/browse/RF-8248 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: ALL Reporter: Dave Chen When a user clicks a command link/button, show a model dialog on the top of current page(like modelPanel). The model dialog content should be able to be retrieved from server side by ajax. After filling dialog data, then submit to server side for execution, and update parent page content. Trinidad has a dialog framework. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-4849) Dialog framework

by Nick Belaevski (JIRA)

Dialog framework ---------------- Key: RF-4849 URL: https://jira.jboss.org/jira/browse/RF-4849 Project: RichFaces Issue Type: Feature Request Affects Versions: Wishes Reporter: Nick Belaevski Fix For: Wishes http://myfaces.apache.org/trinidad/devguide/dialogs.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-8247) add displayValueOnly attribute to all richfaces components

by Dave Chen (JIRA)

add displayValueOnly attribute to all richfaces components ---------------------------------------------------------- Key: RF-8247 URL: https://jira.jboss.org/jira/browse/RF-8247 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: ALL Reporter: Dave Chen A compont can be editing mode for users to input data, or in showing mode for display values only. Attribute "displayValueOnly" will reduce JSF page size and memory size, and simplify programming. For example: for pickList, we have to use two components: one for editing, and one for showing: <rich:pickList rendered="#{bean.isEditing}" value="#{bean.values}" > <f:selectItems value="#{bean.selectItems}"/> </rich:pickList> <h:outputText rendered="#{!bean.isEditing}" value="#{bean.valuesAsString}" /> After adding displayValueOnly, one component will be sufficient, very clean. <rich:pickList rendered="#{bean.isEditing}" value="#{bean.values}" displayValueOnly="#{!bean.isEditing}" > <f:selectItems value="#{bean.selectItems}"/> </rich:pickList> This applies to all components. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-8239) edit api in inplaces should set the focus to input/select

by Ilya Shaikovsky (JIRA)

edit api in inplaces should set the focus to input/select --------------------------------------------------------- Key: RF-8239 URL: https://jira.jboss.org/jira/browse/RF-8239 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 3.3.3.BETA1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Priority: Optional -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-4128) They all should be Trees:Panel Menu, Context Menu, Drop Down

by Francisco Jose Peredo Noguez (JIRA)

They all should be Trees:Panel Menu, Context Menu, Drop Down ------------------------------------------------------------ Key: RF-4128 URL: https://jira.jboss.org/jira/browse/RF-4128 Project: RichFaces Issue Type: Feature Request Reporter: Francisco Jose Peredo Noguez I would like to be able to use recursiveTreeNodesAdaptor to configure Panel Menu, Context Menu, Drop Down Menu, after all, they all are recursive trees. They all should be Trees:Panel Menu, Context Menu, Drop Down Menu. Shouldn't they? Why not? AFAIK there is no easy way to make this possible right now -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2010