August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13052) popupPanel: @visualOptions does not work

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13052?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-13052: ------------------------------- Assignee: Lukáš Fryč > popupPanel: @visualOptions does not work > ---------------------------------------- > > Key: RF-13052 > URL: https://issues.jboss.org/browse/RF-13052 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Jiří Štefek > Assignee: Lukáš Fryč > Fix For: 4.3.4, 5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Setting @visualOptions doesn't work. Tried both settings from https://issues.jboss.org/browse/RF-2464 or https://issues.jboss.org/browse/RF-5239 > e.g.: 'left:1px' > OR > Is this attribute a leftover from older versions of RF (RF-3) and was replaced by attributes @*width, @*height and @style* ? > ALSO UPDATE VDL-DOC in both cases. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13130) Add Hamcrest for BDD-style assertions

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13130: ------------------------------- Summary: Add Hamcrest for BDD-style assertions Key: RF-13130 URL: https://issues.jboss.org/browse/RF-13130 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tests - unit Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 5.0.0.Alpha2 https://code.google.com/p/hamcrest/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13129) Bind Widget Bridge reference to the DOM

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13129: ------------------------------- Summary: Bind Widget Bridge reference to the DOM Key: RF-13129 URL: https://issues.jboss.org/browse/RF-13129 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Lukáš Fryč Fix For: 5.0.0.Alpha2 Following alghoritm looks for the RichFaces component root and re-directs event source to this root: https://github.com/richfaces/richfaces/blob/master/framework/src/main/res... However bridge code isn't registered to the DOM in the way RichFaces 4 using BaseComponent are. I suggest to bind the reference to the DOM using jQuery.data. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13016) Archetypes should be removed from 4.3 build and dist

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13016?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13016: --------------------------------- +1 > Archetypes should be removed from 4.3 build and dist > ---------------------------------------------------- > > Key: RF-13016 > URL: https://issues.jboss.org/browse/RF-13016 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.3.2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Archetypes will now have independent release cycle. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13016) Archetypes should be removed from 4.3 build and dist

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13016?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13016: ---------------------------- Fix Version/s: 4.5.0.Alpha1 (was: 4.3.4) > Archetypes should be removed from 4.3 build and dist > ---------------------------------------------------- > > Key: RF-13016 > URL: https://issues.jboss.org/browse/RF-13016 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.3.2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Archetypes will now have independent release cycle. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState

by Steven W. (JIRA)

[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ] Steven W. commented on RF-13126: -------------------------------- Hi - those 2 (F-13094 + RF-13095) may cover it - presuming that they're not just for 4.3.4 but also targeting 5.x base. Thanks, Steve > ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState > ---------------------------------------------------------------------------------------------------------- > > Key: RF-13126 > URL: https://issues.jboss.org/browse/RF-13126 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 5.0.0.Alpha1 > Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE) > Reporter: Steven W. > Labels: waiting_on_user > > In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size. > In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be RF-4855 + RF-13094 and RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release. > I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this column header sizing AND/OR TableState table header sizing issue(s) still remain, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState

by Steven W. (JIRA)

[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ] Steven W. edited comment on RF-13126 at 8/12/13 8:57 PM: --------------------------------------------------------- Hi - those 2 (RF-13094 + RF-13095) may cover it - presuming that they're not just for 4.3.4 but also targeting 5.x base. Thanks, Steve was (Author: entracity): Hi - those 2 (F-13094 + RF-13095) may cover it - presuming that they're not just for 4.3.4 but also targeting 5.x base. Thanks, Steve > ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState > ---------------------------------------------------------------------------------------------------------- > > Key: RF-13126 > URL: https://issues.jboss.org/browse/RF-13126 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 5.0.0.Alpha1 > Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE) > Reporter: Steven W. > Labels: waiting_on_user > > In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size. > In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be RF-4855 + RF-13094 and RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release. > I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this column header sizing AND/OR TableState table header sizing issue(s) still remain, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13016) Archetypes should be removed from 4.3 build and dist

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13016?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13016: ---------------------------------- Assignee: Lukáš Fryč (was: Brian Leathem) IMO this change should be applied in RF 4.5/5.0, not in 4.3. > Archetypes should be removed from 4.3 build and dist > ---------------------------------------------------- > > Key: RF-13016 > URL: https://issues.jboss.org/browse/RF-13016 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.3.2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Archetypes will now have independent release cycle. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13125: ---------------------------------- Assignee: Lukáš Fryč > a4j:log does swallow the message from jsf.js's sendError method > --------------------------------------------------------------- > > Key: RF-13125 > URL: https://issues.jboss.org/browse/RF-13125 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.3, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > {code:title=jsf.js:2220} > } catch (ex) { > sendError(request, context, "malformedXML", ex.message); > return; > } > {code} > The ex.message is not shown in output of a4j:log. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13038) Command button/link: attribute tabindex missing

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13038?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13038. -------------------------------- Resolution: Done Added the tabindex attribute to CommandLink and CommandButton. > Command button/link: attribute tabindex missing > ----------------------------------------------- > > Key: RF-13038 > URL: https://issues.jboss.org/browse/RF-13038 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Components command button and command link don't have attribute "tabindex", however, when it's set on the component, it's rendered correctly. This issue is similar to one for accesskey attribute (RF-12846). -- 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, 3 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 August 2013