February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12304) A javascript error is thrown when the number of frozen columns = total number of columns

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12304?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12304: ------------------------------- Fix Version/s: (was: 4.2.5) > A javascript error is thrown when the number of frozen columns = total number of columns > ---------------------------------------------------------------------------------------- > > Key: RF-12304 > URL: https://issues.jboss.org/browse/RF-12304 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.2.Final > Environment: jetty + tomcat 6 on win 7 > tomcat + Chrome + Linux > Reporter: Britt Abel > Labels: richfaces > Attachments: error.png > > > If I place two or more extendedDataTables with selectionType="single" on one a page, it is only possible to make a selection on the first extendedDataTable. It is imposible to select a row on the second table. If I turn around the order of tables or delete the first one, it works fine for the other one. This means, the implementation itself shoul be correct, > Do you have any ideas? Thanks for your help!!! -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12304) A javascript error is thrown when the number of frozen columns = total number of columns

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12304?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-12304: ---------------------------------------------- Brian Leathem <bleathem(a)redhat.com> made a comment on [bug 871933|https://bugzilla.redhat.com/show_bug.cgi?id=871933] Any update on this issue? Can we indeed close it? > A javascript error is thrown when the number of frozen columns = total number of columns > ---------------------------------------------------------------------------------------- > > Key: RF-12304 > URL: https://issues.jboss.org/browse/RF-12304 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.2.Final > Environment: jetty + tomcat 6 on win 7 > tomcat + Chrome + Linux > Reporter: Britt Abel > Labels: richfaces > Fix For: 4.2.5 > > Attachments: error.png > > > If I place two or more extendedDataTables with selectionType="single" on one a page, it is only possible to make a selection on the first extendedDataTable. It is imposible to select a row on the second table. If I turn around the order of tables or delete the first one, it works fine for the other one. This means, the implementation itself shoul be correct, > Do you have any ideas? Thanks for your help!!! -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ] Ken Finnigan updated RF-12768: ------------------------------ Fix Version/s: 4.3-Tracking > Metamer: rich:tabPanel: Tabs are not clickable and can't be removed > ------------------------------------------------------------------- > > Key: RF-12768 > URL: https://issues.jboss.org/browse/RF-12768 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Labels: richfaces4 > Fix For: 4.3-Tracking > > > Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12766) Metamer: a4j:log doesn't work with popup option

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/RF-12766?page=com.atlassian.jira.plugin.s... ] Ken Finnigan updated RF-12766: ------------------------------ Fix Version/s: 4.3-Tracking > Metamer: a4j:log doesn't work with popup option > ----------------------------------------------- > > Key: RF-12766 > URL: https://issues.jboss.org/browse/RF-12766 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.0.3, JPP 6.0 EPP 05, Firefox 18.0.1 > Reporter: Petr Mensik > Labels: a4j:log, jpp-6.0, metamer, richfaces > Fix For: 4.3-Tracking > > > This bug is connected with a4j:log component. When you set a mode attribute to popup and then do some action, nothing happens. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12592) rich:contextMenu clipped by rich:extendedDataTable cells.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12592?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12592. -------------------------------- Fix Version/s: (was: 4.2.4) Resolution: Duplicate Issue > rich:contextMenu clipped by rich:extendedDataTable cells. > --------------------------------------------------------- > > Key: RF-12592 > URL: https://issues.jboss.org/browse/RF-12592 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.2.Final > Environment: browsers: Chrome, Firefox > application container: EAP 6 > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Attachments: brokenContextMenu.png, dataTable.png, dataTable.xhtml, extendedDataTable.png > > > The context menu gets clipped by extendedDataTable cells. The same code works fine with RF3 (see the attached screenshots and test page). The context menu is correctly displayed if extendedDataTable is replaced with dataTable (attached dataTable.png). -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12767) Metamer: rich:collapsibleSubTable don't work with rich:dataScroller

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/RF-12767?page=com.atlassian.jira.plugin.s... ] Ken Finnigan updated RF-12767: ------------------------------ Fix Version/s: 4.3-Tracking > Metamer: rich:collapsibleSubTable don't work with rich:dataScroller > -------------------------------------------------------------------- > > Key: RF-12767 > URL: https://issues.jboss.org/browse/RF-12767 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.0.4 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Labels: jboss-as7, richfaces > Fix For: 4.3-Tracking > > > As title suggested, data scrolling is not working in rich:collapsibleSubTable. You can move to the second page but after that the scroll panel gets frozen and you can move only to first page again. Same thing occurs of you click for example to page 5, you can only move backwards. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12252) kitchensink archetype - creating already registered user throws server side error - it should be caught and user should be noticed

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12252?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12252: ------------------------------- Fix Version/s: 4.3.0.M3 > kitchensink archetype - creating already registered user throws server side error - it should be caught and user should be noticed > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12252 > URL: https://issues.jboss.org/browse/RF-12252 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.2.2.Final > Environment: project generated from kitchensink archetype > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Minor > Fix For: 4.2.4, 4.3.0.M3 > > > When creating an already registered user there is server side error, because of the not unique email: > {code} > javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: Unique index or primary key violation: "CONSTRAINT_INDEX_8 ON PUBLIC.MEMBER(EMAIL)"; SQL statement: > {code} > There is also no error message rendered to the user. There should be some notice that such a user have been already registered. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12792) ContextMenu - onkeydown attribute does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12792?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12792: ------------------------------------ [~jhuska] can you check if this works in an earlier release of richfaces? > ContextMenu - onkeydown attribute does not work > ----------------------------------------------- > > Key: RF-12792 > URL: https://issues.jboss.org/browse/RF-12792 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.0.Final > Environment: RichFaces 4.3.1-SNAPSHOT > Metamer 4.3.1-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Chrome 24.0.1312.69 @ Linux x86_64 > Reporter: Juraj Húska > > The {{onkeydown}} attribute does not work. > Just note that {{onkeyup}} work just fine. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12792) ContextMenu - onkeydown attribute does not work

by Juraj Húska (JIRA)

Juraj Húska created RF-12792: -------------------------------- Summary: ContextMenu - onkeydown attribute does not work Key: RF-12792 URL: https://issues.jboss.org/browse/RF-12792 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.3.0.Final Environment: RichFaces 4.3.1-SNAPSHOT Metamer 4.3.1-SNAPSHOT JBoss Application Server: Weld Integration 7.1.1.Final JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux Chrome 24.0.1312.69 @ Linux x86_64 Reporter: Juraj Húska The {{onkeydown}} attribute does not work. Just note that {{onkeyup}} work just fine. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12791) Update the quickstart pom files to match changes made in the jboss-jdf repository

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/RF-12791?page=com.atlassian.jira.plugin.s... ] Sande Gilda updated RF-12791: ----------------------------- Description: There were numerous changes to the quickstart pom files: - property names were shortened and standardized - property versions were updated - comments were standardized around product/community version numbers It may be easiest just to copy and paste the corresponding jboss-jdf quickstart pom.xml files into your repository, however, these are the commits: https://github.com/sgilda/quickstart/commit/ca2a7bea84262a7aa28b082760746... https://github.com/sgilda/quickstart/commit/d951d07c1a2e980b0550ff62145cf... was: There were numerous changes to the quickstart pom files: - property names were shortened and standardized - property versions were updated - comments were standardized around product/community version numbers It may be easiest just to copy and paste the corresponding quickstart pom.xml files from jboss-jdf into your repository. > Update the quickstart pom files to match changes made in the jboss-jdf repository > --------------------------------------------------------------------------------- > > Key: RF-12791 > URL: https://issues.jboss.org/browse/RF-12791 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > > There were numerous changes to the quickstart pom files: > - property names were shortened and standardized > - property versions were updated > - comments were standardized around product/community version numbers > It may be easiest just to copy and paste the corresponding jboss-jdf quickstart pom.xml files into your repository, however, these are the commits: > https://github.com/sgilda/quickstart/commit/ca2a7bea84262a7aa28b082760746... > https://github.com/sgilda/quickstart/commit/d951d07c1a2e980b0550ff62145cf... -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2013