October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12952) Favor Props interfaces over attrs.xml

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-12952?page=com.atlassian.jira.plugin.s... ] Matej Novotny updated RF-12952: ------------------------------- Labels: (was: needs-qe) > Favor Props interfaces over attrs.xml > ------------------------------------- > > Key: RF-12952 > URL: https://issues.jboss.org/browse/RF-12952 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Lukáš Fryč > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > We should favor {{*Props}} interfaces since they are refactorable. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12952) Favor Props interfaces over attrs.xml

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-12952?page=com.atlassian.jira.plugin.s... ] Matej Novotny commented on RF-12952: ------------------------------------ Change verified, issue can be closed. > Favor Props interfaces over attrs.xml > ------------------------------------- > > Key: RF-12952 > URL: https://issues.jboss.org/browse/RF-12952 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Lukáš Fryč > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > We should favor {{*Props}} interfaces since they are refactorable. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13231) RF 5, tree component missing resource

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13231?page=com.atlassian.jira.plugin.s... ] Matej Novotny commented on RF-13231: ------------------------------------ Verified, works correctly now. Issue can be closed. > RF 5, tree component missing resource > ------------------------------------- > > Key: RF-13231 > URL: https://issues.jboss.org/browse/RF-13231 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux > Chrome 29.0.1547.76 @ Linux x86_64 > Reporter: Matej Novotny > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Using Metamer I accesed a tree component (see steps to reproduce) and it did not render properly, therefore the tree was not usable. > The error message in web console was: > GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 500 (Internal Server Error) > This may be also connected to https://issues.jboss.org/browse/RF-13200 -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-13082 at 10/3/13 1:43 AM: ------------------------------------------------------------- A orderingList prototype component is available on the sandbox master branch in the "selects" sandbox project. was (Author: bleathem): A orderingList prototype component is available on the sandbox master branch > Change the orderingList component to use the new orderingList widget > -------------------------------------------------------------------- > > Key: RF-13082 > URL: https://issues.jboss.org/browse/RF-13082 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Attributes to be dropped in the RF5 implementation: > * disabledClass > * headerClass > * itemClass > * selectItemClass > * listHeight > * listWidth > * listMaxHeight > * listMaxWidth > It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_). > Similarly the height/width CSS attributes are better set with CSS styles, rather than via facelet attributes. > Additionally, we should consider dropping the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover? -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13083) Change the pickList component to use the new pickList widget

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13083?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13083: ------------------------------------ A pickList prototype component is available on the sandbox master branch in the "selects" sandbox project. > Change the pickList component to use the new pickList widget > ------------------------------------------------------------ > > Key: RF-13083 > URL: https://issues.jboss.org/browse/RF-13083 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13082: ------------------------------------ A orderingList prototype component is available on the sandbox master branch > Change the orderingList component to use the new orderingList widget > -------------------------------------------------------------------- > > Key: RF-13082 > URL: https://issues.jboss.org/browse/RF-13082 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Attributes to be dropped in the RF5 implementation: > * disabledClass > * headerClass > * itemClass > * selectItemClass > * listHeight > * listWidth > * listMaxHeight > * listMaxWidth > It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_). > Similarly the height/width CSS attributes are better set with CSS styles, rather than via facelet attributes. > Additionally, we should consider dropping the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover? -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13234) Internet Explorer 8 dialogwindow not opening

by Prasanna Subramanian (JIRA)

[ https://issues.jboss.org/browse/RF-13234?page=com.atlassian.jira.plugin.s... ] Prasanna Subramanian commented on RF-13234: ------------------------------------------- Hi Brian Leathem, Thanks For your Reply...Let me know that rich:fileupload component we need to any configure for open/browse the files ?... in Internet Explorer 8 Browser settings. > Internet Explorer 8 dialogwindow not opening > -------------------------------------------- > > Key: RF-13234 > URL: https://issues.jboss.org/browse/RF-13234 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 3.3.3.Final > Reporter: Prasanna Subramanian > Fix For: 3.Future > > > Hi, > I am using rich:fileupload in my web application....we using only internet explorer 8 > My browser alone not open the dialog window.....to select the files ,but other computer with same browser(IE8) is opening....to select the files. > Let me know, any options i need to change in Internet explorer 8 for rich:fileupload component to open the file browser....... -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12977) a4j:queue breaks tabPanel

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12977?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12977: ------------------------------------ Thank for both reproducing and finding the existing issue [~jhuska]! > a4j:queue breaks tabPanel > ------------------------- > > Key: RF-12977 > URL: https://issues.jboss.org/browse/RF-12977 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.2, 5.0.0.Alpha2 > Environment: This happens in RF 4.3.2.CR1, but I can't select such version in JIRA. > Reporter: Bernard Labno > Priority: Critical > Fix For: 5.0.0.Alpha3 > > > There is clearly a bug in tabPanel.js > {code} > execAjax : function (oldPanel, newPanel) { > var options = $.extend({}, newPanel.getTogglePanel().options["ajax"], {}); > this.__setActiveItem(newPanel); > rf.ajax(newPanel.id, null, options); > if (oldPanel) { // HERE IS THE BUG > this.__setActiveItem(oldPanel); > } > return false; > }, > {code} > If the tab panel works in ajax mode and we attach a4j:queue with requestDelay="1000" then rf.ajax... will just add request to queue, but meanwhile the active item will be changed to old value. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12977) a4j:queue breaks tabPanel

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12977?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12977: ------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 5-Tracking) > a4j:queue breaks tabPanel > ------------------------- > > Key: RF-12977 > URL: https://issues.jboss.org/browse/RF-12977 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.2, 5.0.0.Alpha2 > Environment: This happens in RF 4.3.2.CR1, but I can't select such version in JIRA. > Reporter: Bernard Labno > Priority: Critical > Fix For: 5.0.0.Alpha3 > > > There is clearly a bug in tabPanel.js > {code} > execAjax : function (oldPanel, newPanel) { > var options = $.extend({}, newPanel.getTogglePanel().options["ajax"], {}); > this.__setActiveItem(newPanel); > rf.ajax(newPanel.id, null, options); > if (oldPanel) { // HERE IS THE BUG > this.__setActiveItem(oldPanel); > } > return false; > }, > {code} > If the tab panel works in ajax mode and we attach a4j:queue with requestDelay="1000" then rf.ajax... will just add request to queue, but meanwhile the active item will be changed to old value. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13220) Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/RF-13220?page=com.atlassian.jira.plugin.s... ] Sande Gilda commented on RF-13220: ---------------------------------- In addition to removing references to AS 7, we need to do the following: Add the following metadata tag: Product Versions: EAP 6.1, EAP 6.2, RichFaces <version> Under System Requirements, add: The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform (EAP) 6.1 or later. Remove all other references to EAP versions so we don't have to maintain them throughout the code. See this commit for the WFK changes: https://github.com/sgilda/jboss-wfk-quickstarts/commit/933e88e01123308535... [~vineet.reynolds]: Please let me know if you need any help. > Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts > --------------------------------------------------------------------- > > Key: RF-13220 > URL: https://issues.jboss.org/browse/RF-13220 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Assignee: Vineet Reynolds > > The readme files provide instruction on how to run quickstarts on both AS 7.1 and EAP 6. Quickstarts now target EAP 6.1, so we need to remove references to AS 7.1. -- 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

11 years, 4 months

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 October 2013