November 2013 - richfaces-issues - Jboss List Archives

[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: ------------------------------------ We need the wrapper div to hold the clientId, as the list gets wrapped by DOM elements in the widget initialisation. I have some ideas of how to improve this, but they are out of scope for RichWidgets 0.1. > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13343: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 8 > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13395) Showcase 4.5.x, input number slider

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13395: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 8 > Showcase 4.5.x, input number slider > ----------------------------------- > > Key: RF-13395 > URL: https://issues.jboss.org/browse/RF-13395 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.5.0.Alpha1 > Environment: JBoss AS 7.1 > Firefox 25 > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186]. > It is about a RF 4.5.x Showcase. > The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186. > {code} > <context-param> > <param-name>javax.faces.PROJECT_STAGE</param-name> > <param-value>Production</param-value> > </context-param> > {code} > Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code). > {code} > Uncaught TypeError: Object [object Object] has no method 'setPosition' inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145 > {code} > The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/re...] line on GitHub. > Otherwise I found no problems/errors/warnings. -- 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, 4 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 updated RF-13393: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 8 > 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, 4 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12224: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 8 > 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 > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13394: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 8 > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordio... > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13395) Showcase 4.5.x, input number slider

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13395: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Showcase 4.5.x, input number slider > ----------------------------------- > > Key: RF-13395 > URL: https://issues.jboss.org/browse/RF-13395 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.5.0.Alpha1 > Environment: JBoss AS 7.1 > Firefox 25 > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186]. > It is about a RF 4.5.x Showcase. > The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186. > {code} > <context-param> > <param-name>javax.faces.PROJECT_STAGE</param-name> > <param-value>Production</param-value> > </context-param> > {code} > Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code). > {code} > Uncaught TypeError: Object [object Object] has no method 'setPosition' inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145 > {code} > The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/re...] line on GitHub. > Otherwise I found no problems/errors/warnings. -- 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, 4 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 updated RF-13393: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13343: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13394: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordio... > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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, 4 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