August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12989) Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final

by Andrea Martino (JIRA)

[ https://issues.jboss.org/browse/RF-12989?page=com.atlassian.jira.plugin.s... ] Andrea Martino commented on RF-12989: ------------------------------------- Hi Brian, in my JSF page I have a button that shows/hides the togglePanelItems rich:toggleControl. More specifically (when it does not work): {code:xml} <rich:togglePanel id="fieldsPanel" activeItem="closed"> <rich:togglePanelItem name="closed"> <h:commandButton value="Show fields" styleClass="submit"> <rich:toggleControl targetItem="checkboxes" /> </h:commandButton> </rich:togglePanelItem> <rich:togglePanelItem name="checkboxes"> Lorem ipsum dolor sit amet, ... </rich:togglePanelItem> </rich:togglePanel> {code} When I click on the "Show fields" button (in the first item), nothing happens. Despite the functionality not working (i.e. by clicking on the button nothing happens), the page renders fine. > Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final > ------------------------------------------------------------------------------------------------------ > > Key: RF-12989 > URL: https://issues.jboss.org/browse/RF-12989 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.Final > Environment: JBossAS 7.1.1 > Reporter: Andrea Martino > Assignee: Brian Leathem > Priority: Minor > Labels: togglePanel, waiting_on_user > Fix For: 4.3.4 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > In RichFaces 4.2.2 it was possible to define togglePane items using id as attribute, as following {code}<rich:togglePanelItem id="item1">{code} > With RichFaces 4.3.0 the page does not work anymore, I had to change the attribute to name {code}<rich:togglePanelItem name="item1">{code} > The docs still say id is valid, even when it's not [http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht...]. Either the docs should be changed or id attribute should be accepted as it was before. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12675: ------------------------------- Assignee: Lukáš Fryč (was: Brian Leathem) > Drag and drop doesn't work with MyFaces > --------------------------------------- > > Key: RF-12675 > URL: https://issues.jboss.org/browse/RF-12675 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Assignee: Lukáš Fryč > Labels: Drag, drop, myfaces > Fix For: 4.3.4, 5-Tracking > > Attachments: dragAndDrop.zip, dragdrop-test.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event: > Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)). > This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces. -- 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

12 years, 7 months

1
0
0 / 0

[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č commented on RF-13052: --------------------------------- Hmm, during removing of the logic I discovered this attribute was partially implemented but it seems it never worked okay (RF-10697). It suppose to save a visual state sent from a client, but this state is not sent anyhow (rendered markup does not contain any input fields which would bear a state). Thus I [came to conclusion|https://issues.jboss.org/browse/RF-10697?focusedCommentId=1279...] it would be save to remove both @visualOptions and @keepVisualState. At the end I believe we should hide the attribute first and then remove it in RichFaces 5. > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-10697) Popup Panel - @keepVisualState does not work

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-10697?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-10697: --------------------------------- I consider using @keepVisualState an anti-pattern, as the result of form submission, people should either: 1. succeed and relocate to another page (where popupPanel should not be opened anymore) 2. fail (validation, business logic error) and stay on the page (update the messages, etc.) Even though I can see use cases where keepVisualState could work, they are rather artificial and since no one has requested this fix (no votes / watchers / comments) I suggest to remove this attribute and accompanied functionality in RichFaces 5. We can hide this attribute in RichFaces 4.3 / 4.5 to prevent harmful changes. > Popup Panel - @keepVisualState does not work > -------------------------------------------- > > Key: RF-10697 > URL: https://issues.jboss.org/browse/RF-10697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: RichFaces 4.0.0.20110227-CR1 r.21967 > Metamer 4.0.0.20110228-CR1 r.21993 > Apache MyFaces JSF-2.0 Core Impl 2.0.4 > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @Linux > Chrome 9.0.597.107 @ Linux x86_64 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Fix @keepVisualState attribute or remove it from taglib. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-10697) Popup Panel - @keepVisualState does not work

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-10697?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-10697 at 8/15/13 2:59 AM: ---------------------------------------------------------- The popup panel's visual state is not sent to the server because the markup doesn't contain [any markup|https://github.com/richfaces4/components/blob/master/output/ui/src...] which would pass the value to the [doDecode method|https://github.com/richfaces4/components/blob/master/output/ui/src...]. So even though {{@domElementAttachment=form}} submits allows to submit a form, the client-side state is not updated. was (Author: lfryc): The popup panel's visual state is not sent to the server because the markup doesn't contain [any markup|https://github.com/richfaces4/components/blob/master/output/ui/src...] which would pass the value to the [doDecode method|https://github.com/richfaces4/components/blob/master/output/ui/src...]. > Popup Panel - @keepVisualState does not work > -------------------------------------------- > > Key: RF-10697 > URL: https://issues.jboss.org/browse/RF-10697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: RichFaces 4.0.0.20110227-CR1 r.21967 > Metamer 4.0.0.20110228-CR1 r.21993 > Apache MyFaces JSF-2.0 Core Impl 2.0.4 > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @Linux > Chrome 9.0.597.107 @ Linux x86_64 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Fix @keepVisualState attribute or remove it from taglib. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-10697) Popup Panel - @keepVisualState does not work

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-10697?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-10697: --------------------------------- The popup panel's visual state is not sent to the server because the markup doesn't contain [any markup|https://github.com/richfaces4/components/blob/master/output/ui/src...] which would pass the value to the [doDecode method|https://github.com/richfaces4/components/blob/master/output/ui/src...]. > Popup Panel - @keepVisualState does not work > -------------------------------------------- > > Key: RF-10697 > URL: https://issues.jboss.org/browse/RF-10697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: RichFaces 4.0.0.20110227-CR1 r.21967 > Metamer 4.0.0.20110228-CR1 r.21993 > Apache MyFaces JSF-2.0 Core Impl 2.0.4 > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @Linux > Chrome 9.0.597.107 @ Linux x86_64 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Fix @keepVisualState attribute or remove it from taglib. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12675: ------------------------------------ I committed a test based off of the provided sample: https://github.com/richfaces4/components/commit/c89dadfbbff57878bc304e533... The test passes fine on JBoss AS EAP 6.1, next step is to get it to run on Tomcat with MyFaces. > Drag and drop doesn't work with MyFaces > --------------------------------------- > > Key: RF-12675 > URL: https://issues.jboss.org/browse/RF-12675 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Assignee: Brian Leathem > Labels: Drag, drop, myfaces > Fix For: 4.3.4, 5-Tracking > > Attachments: dragAndDrop.zip, dragdrop-test.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event: > Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)). > This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12675: ---------------------------------- Assignee: Brian Leathem > Drag and drop doesn't work with MyFaces > --------------------------------------- > > Key: RF-12675 > URL: https://issues.jboss.org/browse/RF-12675 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Assignee: Brian Leathem > Labels: Drag, drop, myfaces > Fix For: 4.3.4, 5-Tracking > > Attachments: dragAndDrop.zip, dragdrop-test.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event: > Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)). > This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13094) Wrong extendedDataTable header widths when narrowing columns

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13094?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13094. -------------------------------- Resolution: Done Used jquery to set the column div width, and also set the column div parent (td) width > Wrong extendedDataTable header widths when narrowing columns > ------------------------------------------------------------ > > Key: RF-13094 > URL: https://issues.jboss.org/browse/RF-13094 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.2 > Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23, tested on Firefox 22 and Chrome 28. > Reporter: Salvo Isaja > Assignee: Brian Leathem > Fix For: 4.3.4 > > Attachments: Layout.jpg > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When reducing column widths on an extendedDataTable narrower than the viewport, columns of the table body are resized correctly, but the columns in the table header stay larger, until the viewport is narrowed too. > This is reproducible in the online RichFaces 4.3.2 showcase with no modifications. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13095) extendedDataTable tableState setter not called on column resize/reorder

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13095?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13095: ------------------------------- Labels: waiting_on_user (was: ) > extendedDataTable tableState setter not called on column resize/reorder > ----------------------------------------------------------------------- > > Key: RF-13095 > URL: https://issues.jboss.org/browse/RF-13095 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.2 > Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23, tested on Firefox 22 and Chrome 28. > Reporter: Salvo Isaja > Assignee: Brian Leathem > Labels: waiting_on_user > Fix For: 4.3.4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Not sure if this qualifies as a bug or a feature request. > I have an extendedDataTable with the tableState attribute bound to a String property of a backing bean (tried both a request scoped bean on a transient view and a session scoped bean on a stateful view). > When resizing or reordering columns, an Ajax request is posted to the server, and I correctly see the new column layouts in the request, but the setter of the tableState property in the backing bean is not called. If I execute @form on a a4j:commandLink or commandButton, it is called instead. > Thanks -- 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

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2013