November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13396) Port patches from 4.5 to 5.0.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13396: ---------------------------- Summary: Port patches from 4.5 to 5.0. (was: Identify patches that needs to be ported from 4.5 to 5.0.) > Port patches from 4.5 to 5.0. > ----------------------------- > > Key: RF-13396 > URL: https://issues.jboss.org/browse/RF-13396 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.5-Tracking, 5-Tracking > Reporter: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > Identify what changes/features need to be ported from RF 4.5 TO RF 5. > Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224]) > If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13090) <rich:jQuery> named functions not working as documented

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13090?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13090: ---------------------------- Fix Version/s: 5.0.0.Alpha2 > <rich:jQuery> named functions not working as documented > ------------------------------------------------------- > > Key: RF-13090 > URL: https://issues.jboss.org/browse/RF-13090 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.2 > Reporter: Vincent Wülcknitz > Assignee: Vincent Wülcknitz > Priority: Minor > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I have found some strange behaviour with the <rich:jQuery> component when you implement named functions like described in the component reference: > http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht... > If I implement the given code from the reference: > {code} > <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this)" /> > <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this)" /> > ... > <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" /> > <rich:jQuery name="releasePic" query="animate({width:'50px'})"/> > {code} > only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout. > I found out that if I do some small changes to the onmouseout call it works fine: > {code} > <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this,{})" /> > <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this,{})" /> > ... > <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" /> > <rich:jQuery name="releasePic" query="animate({width:'50px'})"/> > {code} > It only works when adding a second parameter to the call even if its empty. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12224) fileUpload: Multiple file selection

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12224: --------------------------------- I have introduced support to RF 5 Core + FileUpload component. Additionally, I have fixed support in RF 4.5. It was caused by wrong refactoring here: https://github.com/richfaces4/components/commit/f936e60797c037643937f1eed... > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Simone Cinti > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12224) fileUpload: Multiple file selection

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12224. ----------------------------- Resolution: Done > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Simone Cinti > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12224) fileUpload: Multiple file selection

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12224: ---------------------------- Fix Version/s: 5.0.0.Alpha2 > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12224) fileUpload: Multiple file selection

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12224: ---------------------------- Assignee: Simone Cinti (was: Lukáš Fryč) > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Simone Cinti > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13396) Identify patches that needs to be ported from 4.5 to 5.0.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13396: --------------------------------- RF-12224 fileUpload: Multiple file selection - https://github.com/richfaces4/components/commit/72417a985e2aa9ef9ee316344... RF-13090 Fixed <rich:jQuery> default argument. - https://github.com/richfaces4/components/commit/4bb0d43e4ea48fabfa64b6293... > Identify patches that needs to be ported from 4.5 to 5.0. > --------------------------------------------------------- > > Key: RF-13396 > URL: https://issues.jboss.org/browse/RF-13396 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.5-Tracking, 5-Tracking > Reporter: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > Identify what changes/features need to be ported from RF 4.5 TO RF 5. > Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224]) > If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13392) TreeSelectionChangeEvent always triggered during Apply Request Phase

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13392?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13392: ------------------------------- Fix Version/s: 5-Tracking > TreeSelectionChangeEvent always triggered during Apply Request Phase > -------------------------------------------------------------------- > > Key: RF-13392 > URL: https://issues.jboss.org/browse/RF-13392 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.3.3 > Reporter: Andreas Hahne > Labels: richfaces, selectionChangeListener, tree > Fix For: 5-Tracking > > Attachments: tree.zip > > > When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false. > This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13396) Identify patches that needs to be ported from 4.5 to 5.0.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13396: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Identify patches that needs to be ported from 4.5 to 5.0. > --------------------------------------------------------- > > Key: RF-13396 > URL: https://issues.jboss.org/browse/RF-13396 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.5-Tracking, 5-Tracking > Reporter: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > Identify what changes/features need to be ported from RF 4.5 TO RF 5. > Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224]) > If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13393) orderingList: JavaScript api is bound to wrong element

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13393: ------------------------------------ The fix here is to look up the top-level CDK div via the clientId, and change [this line|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] to store the widget in that element, rather than the list element. > orderingList: JavaScript api is bound to wrong element > ------------------------------------------------------ > > Key: RF-13393 > URL: https://issues.jboss.org/browse/RF-13393 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Michal Petrov > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2013