August 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12114) Richfaces 4.2 rich:autocomplete don't fire ajax on blur event

by Ivan Costa (JIRA)

Ivan Costa created RF-12114: ------------------------------- Summary: Richfaces 4.2 rich:autocomplete don't fire ajax on blur event Key: RF-12114 URL: https://issues.jboss.org/browse/RF-12114 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, component-input Affects Versions: 4.2.0.Final Environment: Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 Reporter: Ivan Costa rich:autocomplete don´t call actionListener on blur event -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
14
0 / 0

[JBoss JIRA] (RF-12259) CDK: full support for iterative/dynamic components

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12259: ------------------------------- Summary: CDK: full support for iterative/dynamic components Key: RF-12259 URL: https://issues.jboss.org/browse/RF-12259 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč There are two kinds of iteration components: * iterative out of the box ** tables ** trees * iteration over children ** tabs ** panel menus ** etc. Both approaches should be supported by CDK -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
13
0 / 0

[JBoss JIRA] (RF-12304) Two or more rich:extendedDataTable on page prevent selection on second extendedDataTable

by Britt Abel (JIRA)

Britt Abel created RF-12304: ------------------------------- Summary: Two or more rich:extendedDataTable on page prevent selection on second extendedDataTable 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 Reporter: Britt Abel 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
21
0 / 0

[JBoss JIRA] (RF-12253) kitchensink archetype - it should be possible to return from viewing details about member back to the list of members on mobile devices

by Juraj Huska (JIRA)

Juraj Huska created RF-12253: -------------------------------- Summary: kitchensink archetype - it should be possible to return from viewing details about member back to the list of members on mobile devices Key: RF-12253 URL: https://issues.jboss.org/browse/RF-12253 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: archetype, mobile Affects Versions: 4.2.2.Final Environment: project generated from kitchensink archetype Reporter: Juraj Huska Priority: Minor When viewing details about created member, it is not possible to return back to the list of all members, but there is only home button. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
11
0 / 0

[JBoss JIRA] (RF-12250) kitchensink archetype - creating new member from iPhone causes broken push update on mobile devices

by Juraj Huska (JIRA)

Juraj Huska created RF-12250: -------------------------------- Summary: kitchensink archetype - creating new member from iPhone causes broken push update on mobile devices Key: RF-12250 URL: https://issues.jboss.org/browse/RF-12250 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype, component-push/poll, mobile Affects Versions: 4.2.2.Final Environment: iPhone, Motorola Xoom application container: JBoss AS 7.1.1.Final. Reporter: Juraj Huska Creating a new member from iPhone device causes that update on mobile devices does not work properly. The list of new members is not updated anymore, even when creating a new members from desktop browsers. No error is thrown either on server or client side. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
26
0 / 0

[JBoss JIRA] Created: (RF-7706) Last focused control should not be lost after a AJAX request (Richfaces should transparently preserve it)

by Francisco Jose Peredo Noguez (JIRA)

Last focused control should not be lost after a AJAX request (Richfaces should transparently preserve it) --------------------------------------------------------------------------------------------------------- Key: RF-7706 URL: https://jira.jboss.org/jira/browse/RF-7706 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Reporter: Francisco Jose Peredo Noguez The focused control before an AJAX request should automatically be the focused control after the request. -- 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

12 years, 1 month

5
15
0 / 0

[JBoss JIRA] Created: (RF-8606) FocusManager component

by Nick Belaevski (JIRA)

FocusManager component ---------------------- Key: RF-8606 URL: https://jira.jboss.org/jira/browse/RF-8606 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.ALPHA2 Reporter: Nick Belaevski Assignee: Nick Belaevski Priority: Critical Fix For: 4.0.0.Final Details in the related forum thread. -- 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

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] (RF-11496) mobile showcase - demo a4j:attachQueue - there should be request delay 2 sec when typing to input but there is 0

by Juraj Huska (Created) (JIRA)

mobile showcase - demo a4j:attachQueue - there should be request delay 2 sec when typing to input but there is 0 ---------------------------------------------------------------------------------------------------------------- Key: RF-11496 URL: https://issues.jboss.org/browse/RF-11496 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.1.0.Milestone3 Environment: app: richfaces-showcase-4.1.0.20111011-M3 container: JBoss AS 7.0.2.Final mobile device: iPad Reporter: Juraj Huska When typing to the input in demo for a4j:attachQueue, there should be 2 sec delay to fire request and to render ajax request indicator (Please wait). However there is *no delay*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

10
17
0 / 0

[JBoss JIRA] Created: (RF-9872) Inplace input: ajax request sent when cancel button clicked

by Pavol Pitonak (JIRA)

Inplace input: ajax request sent when cancel button clicked ----------------------------------------------------------- Key: RF-9872 URL: https://jira.jboss.org/browse/RF-9872 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Milestone4 Environment: RichFaces 4.0.0-SNAPSHOT r.20201 Metamer 4.0.0-SNAPSHOT r.20203 Mojarra 2.0.2-FCS GlassFish Server Open Source Edition 3.0.1 OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 7.0.517.44 @ Linux x86_64 Reporter: Pavol Pitonak 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml 2. set showControls=true 3. click on inplace input, change value and click cancel button result: an ajax request is sent (status and time in header change) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
7
0 / 0

[JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up.

by Tom Giberius (JIRA)

Tom Giberius created RF-11916: --------------------------------- Summary: extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up. Key: RF-11916 URL: https://issues.jboss.org/browse/RF-11916 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Giberius Situation: 1) extendDataTable with a verticall ScrollBar 2) Insert or delete record by insert/delete in myBean and by a re-render of the table. 3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records. Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like: render="myTable@rows(myBean.listOfUpdateRows):myColumn" This works fine for already available rows and indeed it is an UPDATE. Also @body, @header and @footer are available for partial table update. I would like to hava a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw" by only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same. It could look like: render="myTable(a)insert(myBean.Row) render="myTable(a)delete(myBean.RowKey) If you have questions I will gladly elaborate on above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2012