December 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13285) The new autocomplete component's CSS does not play nicely with the RichFaces showcase

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13285?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13285. ------------------------------ Verified, closing issue. > The new autocomplete component's CSS does not play nicely with the RichFaces showcase > ------------------------------------------------------------------------------------- > > Key: RF-13285 > URL: https://issues.jboss.org/browse/RF-13285 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 20 minutes > Remaining Estimate: 20 minutes > > There are some sizing and visibility issues that need to be addressed, likely by changing the showcase applications's custom CSS (this was done for the picklist component for example). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13282. ------------------------------ Verified, closing issue. > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13281) orderingList: ordering button's text overflows the button on Firefox

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13281?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13281. ------------------------------ Verified, works correctly on FF now. Closing issue. > orderingList: ordering button's text overflows the button on Firefox > -------------------------------------------------------------------- > > Key: RF-13281 > URL: https://issues.jboss.org/browse/RF-13281 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Environment: RichFaces 5.0.0-SNAPSHOT > Firefox 24 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Attachments: OL.png > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The ordering button's text overflows the button. > Works in Chrome. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13276) Optimized resources should be generated into generated-resources

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13276?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13276. ------------------------------ Verified, closing issue. > Optimized resources should be generated into generated-resources > ---------------------------------------------------------------- > > Key: RF-13276 > URL: https://issues.jboss.org/browse/RF-13276 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13427: ------------------------------------ Given that the server does not know the cell-height content at the time the response is rendered, there is no way to tailor the number of rows rendered to the content height. I suggest you rethink your layout constraint for a fixed hight table. Can you propose a solution (conceptually) for the problem you are describing? > ED, Datatable: table needs to define the number of rows itself when using dataScroller > -------------------------------------------------------------------------------------- > > Key: RF-13427 > URL: https://issues.jboss.org/browse/RF-13427 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Reporter: Anton Bogoslavskyi > Attachments: data-3.png, datatable-1.png > > > I need using pagination for extendedDataTable control. > My row's height depends on the data it contains. > I need the table to be constant height, so I specify the height in css. > I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller. > So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears. > Both situations are not user friendly. > Actually on each page I need the maximum rows number to fit the height. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13427: ------------------------------- Labels: waiting_on_user (was: ) > ED, Datatable: table needs to define the number of rows itself when using dataScroller > -------------------------------------------------------------------------------------- > > Key: RF-13427 > URL: https://issues.jboss.org/browse/RF-13427 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Reporter: Anton Bogoslavskyi > Labels: waiting_on_user > Attachments: data-3.png, datatable-1.png > > > I need using pagination for extendedDataTable control. > My row's height depends on the data it contains. > I need the table to be constant height, so I specify the height in css. > I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller. > So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears. > Both situations are not user friendly. > Actually on each page I need the maximum rows number to fit the height. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13317: ---------------------------- Description: I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: When the response comes back, the data is fine but I get a JSF error saying bq. During update: javax.faces.ViewState not found Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/no...] says: {quote} Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. {quote} was: I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: When the response comes back, the data is fine but I get a JSF error saying bq. During update: javax.faces.ViewState not found Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: {quote} Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. {quote} > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Lukáš Fryč > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/no...] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13197: --------------------------------- https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/rend... > Input with name javax.faces.ViewState is not rendered after submit > ------------------------------------------------------------------ > > Key: RF-13197 > URL: https://issues.jboss.org/browse/RF-13197 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.Alpha4 also GlassFish 4 > Mojarra 2.2 > Chrome, Firefox > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}. > Expected: > After submitting the form, the {{ViewState}} should be updated. > Actual: > Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs. > Please see steps to reproduce. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13317: ---------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 (was: RichFaces 4.3.5 Sprint 1) > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Pavel Slegr > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-13317: ------------------------------- Assignee: Lukáš Fryč (was: Pavel Slegr) > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Lukáš Fryč > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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, 3 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 2013