December 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server

by Ken H (JIRA)

[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ] Ken H commented on RF-12671: ---------------------------- I've tried to trace this around but all I have been able to establish is that the processDrop event never gets queued so it does not get broadcasted in the Invoke Application phase. > dropTarget does not work inside dynamic tabs when switchType is ajax or server > ------------------------------------------------------------------------------ > > Key: RF-12671 > URL: https://issues.jboss.org/browse/RF-12671 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M3 > Reporter: Ken H > > The following works fine: > {code} > <rich:tabPanel switchType="client"> > <a4j:repeat value="#{bean.thingsToIterate}" var="thing"> > <rich:tab header="Tab #{thing}"> > <rich:panel style="width: 100px;"> > <rich:dragSource dragValue="drag-#{thing}" type="term" /> > drag #{thing} > </rich:panel> > <rich:panel style="width: 100px;"> > <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" /> > drop #{thing} > </rich:panel> > </rich:tab> > </a4j:repeat> > </rich:tabPanel> > public void processDrop(DropEvent evt) { > log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue()); > } > {code} > However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-7706) Last focused control should not be lost after a AJAX request (Richfaces should transparently preserve it)

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-7706?page=com.atlassian.jira.plugin.sy... ] Juraj Húska closed RF-7706. --------------------------- > Last focused control should not be lost after a AJAX request (Richfaces should transparently preserve it) > --------------------------------------------------------------------------------------------------------- > > Key: RF-7706 > URL: https://issues.jboss.org/browse/RF-7706 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 3.2.2, 3.3.1 > Reporter: Francisco Jose Peredo Noguez > Assignee: Lukáš Fryč > Fix For: 4.3.0.M3 > > > The focused control before an AJAX request should automatically be the focused control after the request. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12563) Migrate the Placeholder (originally Watermark) component from the sandbox

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12563?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12563. ---------------------------- > Migrate the Placeholder (originally Watermark) component from the sandbox > ------------------------------------------------------------------------- > > Key: RF-12563 > URL: https://issues.jboss.org/browse/RF-12563 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 4.3.0.M3 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12562) Migrate the focus component from the sandbox

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12562?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12562. ---------------------------- > Migrate the focus component from the sandbox > -------------------------------------------- > > Key: RF-12562 > URL: https://issues.jboss.org/browse/RF-12562 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 4.3.0.M3 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12560) showcase - drag and drop - demo with drag indicator throws JS errors when dragging an item

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12560?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12560. ---------------------------- verified > showcase - drag and drop - demo with drag indicator throws JS errors when dragging an item > ------------------------------------------------------------------------------------------ > > Key: RF-12560 > URL: https://issues.jboss.org/browse/RF-12560 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop, showcase > Affects Versions: 4.3.0.M2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final, Tomcat > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Labels: regression > Fix For: 4.3.0.M3 > > Attachments: DAndDError2Firefox.png, dragAndDroperrorChrome.png > > > When attempting to drag an item with support of drag indicators, JS errors are thrown to the console. > Please see the attachments for the errors (they are different on Chrome than on Firefox). The errors are thrown after successfully dragging one item. Then dragging is not working at all. > Drag and Drop demo without drag indicator is working just fine. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12674) Write fundamental tests for Autocomplete tokenizing feature

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12674: ------------------------------- Summary: Write fundamental tests for Autocomplete tokenizing feature Key: RF-12674 URL: https://issues.jboss.org/browse/RF-12674 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: tests - functional Affects Versions: 4.3.0.M3 Reporter: Lukáš Fryč Assignee: Pavol Pitonak According to RF-12664 and meeting discussion, the new tests should be introduced to cover Autocomplete tokenizing feature by fundamental tests. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12664) Showcase - rich:autocomplete - space separator works even when token is set just to comma

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12664?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12664. ----------------------------- Assignee: Lukáš Fryč Fix Version/s: (was: 4.3.0.CR1) Resolution: Rejected According to meeting, this issue is being rejected and RF-12674 was opened to write fundamental tests to cover this behavior. > Showcase - rich:autocomplete - space separator works even when token is set just to comma > ----------------------------------------------------------------------------------------- > > Key: RF-12664 > URL: https://issues.jboss.org/browse/RF-12664 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.3.0.M3 > Environment: Chrome 23 and FF 17 > JBoss AS 7.1.1.Final > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > It works to fill in values in to the autocomplete input separated with spaces, even though the {{token}} attribute is set just to the comma separator. > I tried this behavior when I saw [this|https://github.com/richfaces/showcase/commit/ad703a86ef29a6b41146a9b...] commit merged with upstream and it worked that time. I do not know why it is not working for me with 4.3.M3 release. I tried it also with 4.3.0-SNAPSHOT and the issue is also there. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server

by Ken H (JIRA)

[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ] Ken H commented on RF-12671: ---------------------------- I just wanted to add a minor note that I have used the majority of the other input components inside this ajax-switched dynamic tab configuration without any issue. The issue appears to be something specific to the handling of dropListener. > dropTarget does not work inside dynamic tabs when switchType is ajax or server > ------------------------------------------------------------------------------ > > Key: RF-12671 > URL: https://issues.jboss.org/browse/RF-12671 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M3 > Reporter: Ken H > > The following works fine: > {code} > <rich:tabPanel switchType="client"> > <a4j:repeat value="#{bean.thingsToIterate}" var="thing"> > <rich:tab header="Tab #{thing}"> > <rich:panel style="width: 100px;"> > <rich:dragSource dragValue="drag-#{thing}" type="term" /> > drag #{thing} > </rich:panel> > <rich:panel style="width: 100px;"> > <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" /> > drop #{thing} > </rich:panel> > </rich:tab> > </a4j:repeat> > </rich:tabPanel> > public void processDrop(DropEvent evt) { > log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue()); > } > {code} > However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12654) PartialViewRender skips check for whether column is rendered before checking if children can be rendered

by Ken H (JIRA)

[ https://issues.jboss.org/browse/RF-12654?page=com.atlassian.jira.plugin.s... ] Ken H commented on RF-12654: ---------------------------- The behavior still exists in 4.3.0.M3. > PartialViewRender skips check for whether column is rendered before checking if children can be rendered > -------------------------------------------------------------------------------------------------------- > > Key: RF-12654 > URL: https://issues.jboss.org/browse/RF-12654 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M2 > Environment: JBoss 7.1.1.Final > Reporter: Ken H > Labels: waiting_on_user > > When using rendered on a component within a rich:column of a rich:dataTable, the EL on the component is executed even if the column is not rendered. > The expected behavior (per my loose understanding of the JSF spec) would suggest that the traversal should have short-circuited before checking the unrendered column's children. > This behavior exists at least as far back as 4.1.0.Final. > Given this minimal example: > {code} > <rich:dataTable value="#{bean.foos}" var="foo"> > <rich:column rendered="false"> > <h:outputText value="#{foo.bar}" rendered="#{foo.propertyDoesNotExist != null}" /> > </rich:column> > <rich:column> > <a4j:commandButton value="Test" action="#{bean.noop}" > execute="@this" render="@form" /> > </rich:column> > </rich:dataTable> > {code} > Clicking the Test button would result in a stack trace similar to the following: > {code} > /index.xhtml @33,96 rendered="#{foo.propertyDoesNotExist != null}": The class 'org.richfaces.tests.Foo' does not have the property 'propertyDoesNotExist'. > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:111) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:413) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.isVisitable(UIComponent.java:1669) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1602) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.component.UIDataAdaptor$DataVisitorForVisitTree.process(UIDataAdaptor.java:199) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.ajax4jsf.model.SequenceDataModel.walk(SequenceDataModel.java:65) [richfaces-core-api-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.walk(UIDataAdaptor.java:796) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.visitDataChildren(UIDataAdaptor.java:1269) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataTableBase.visitDataChildren(UIDataTableBase.java:395) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1347) [richfaces-components-ui-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.richfaces.context.ExtendedPartialViewContextImpl.visitActivatorComponent(ExtendedPartialViewContextImpl.java:440) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.visitActivatorAtExecute(ExtendedPartialViewContextImpl.java:310) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.getExecuteIds(ExtendedPartialViewContextImpl.java:98) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at org.richfaces.context.ExtendedPartialViewContextImpl.isExecuteAll(ExtendedPartialViewContextImpl.java:148) [richfaces-core-impl-4.3.0.20121024-M2.jar:4.3.0.20121024-M2] > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:929) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.7-jbossorg-2.jar:] > {code} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12673) Collapsible sub table: filtering doesn't work inside switchable panels

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12673?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-12673: ------------------------------------ Attributes *rows* and *first* don't work, too. > Collapsible sub table: filtering doesn't work inside switchable panels > ---------------------------------------------------------------------- > > Key: RF-12673 > URL: https://issues.jboss.org/browse/RF-12673 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables, regression > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121214-M3 > Mojarra 2.1.7 (bundled in AS) > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.97 @ Linux x86_64 > Reporter: Pavol Pitonak > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richCollapsibleSubTable/fi... > # set attribute rows to 0 > # type "Alexander" into input in first column ("Name") > result: > * table shows 159 result but only 10 should be visible (those containing "Alexander") > * worked fine in 4.3.0.M2 > * doesn't work in all switchable panels - _rich:accordion_, _rich:tabPanel_, _rich:togglePanel_ and _rich:collapsiblePanel_ -- 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

13 years, 4 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 December 2012