November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13340) orderingList - setting of some attributes does not have any effect on the component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13340: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > orderingList - setting of some attributes does not have any effect on the component > ----------------------------------------------------------------------------------- > > Key: RF-13340 > URL: https://issues.jboss.org/browse/RF-13340 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Jiří Štefek > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of these attributes on a {{orderingList}} has no effect on the rendered component > * style > * valueChangeListener -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13346) orderingList - maxListHeight & minListHeight need to have set units along with number to work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13346: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > orderingList - maxListHeight & minListHeight need to have set units along with number to work > --------------------------------------------------------------------------------------------- > > Key: RF-13346 > URL: https://issues.jboss.org/browse/RF-13346 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > {{pickList}} attributes: > * {{minListHeight}} and {{maxListHeight}} > need to have set units along with the number value (e.g. 200px) in order to work correctly. > In RF4 and in RichWidgets, these attributes can be left without units. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13344) pickList - maxListHeight & minListHeight need to have set units along with number to work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13344: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > pickList - maxListHeight & minListHeight need to have set units along with number to work > ----------------------------------------------------------------------------------------- > > Key: RF-13344 > URL: https://issues.jboss.org/browse/RF-13344 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > {{pickList}} attributes: > * {{minListHeight}} and {{maxListHeight}} > need to have set units along with the number value (e.g. 200px) in order to work correctly. > In RF4 and in RichWidgets, these attributes can be left without units. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13257) PhotoAlbum bugs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13257?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13257: ------------------------------- Fix Version/s: 4.3.5 > PhotoAlbum bugs > --------------- > > Key: RF-13257 > URL: https://issues.jboss.org/browse/RF-13257 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Jiří Štefek > Fix For: 4.3.5 > > > PhotoAlbum 4.3.x known bugs: > * uploading file to album (image isn't saved to DB) > * deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13251: ---------------------------------- Assignee: Lukáš Fryč @lfryc please assess and schedule accordingly > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13221) Incorrect XML encoding in AJAX response

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13221?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13221. -------------------------------- Resolution: Rejected Upstream issue. > Incorrect XML encoding in AJAX response > --------------------------------------- > > Key: RF-13221 > URL: https://issues.jboss.org/browse/RF-13221 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Jonáš Trantina > Labels: gss > > Consider the following example: > {noformat} > <h:form> > <a4j:commandButton render="@form" value="rerender me"/> > <script src="path_to_some_script?param=asd&important=param"></script> > </h:form> > {noformat} > when commandButton is clicked, the form is rerendered and the response looks like this: > {noformat} > <partial-response><changes><update id="someID"><![CDATA[ > ... > <script src="path_to_some_script?param=asd&important=param"></script> > ]]</ ... > > {noformat} > But this is wrong. Because script tag is already in CDATA, so there is no need for XML encoding for '&' entity. > This further causes script loading to fail (performed by jsf.js), whenever parameters are needed (e.g. portal environment), > because script is downloaded from {noformat}"path_to_some_script?param=asd&important=param" {noformat} > instead of {noformat}"path_to_some_script?param=asd&important=param"{noformat}. > Another very similar issue is when CDATA element is present in a re-rendered fragment. Example: > {noformat} > <h:form> > <a4j:commandButton render="@form" value="rerender me"/> > <style type="text/css"> > /* <![CDATA[ */ > .somecssclass {...} > /* ]] */ > </style> > </h:form> > {noformat} > The AJAX response then looks like so: > {noformat} > <partial-response><changes><update id="someID"><![CDATA[ > ... > <![CDATA[ > ... > ]] > ... > ]]</ ... > > {noformat} > And this is incorrect XML, since CDATA cannot contain ']]', so the response is discarded. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13244) StyleProps and StyleClassProps should be merged to one interface

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13244?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13244. -------------------------------- Resolution: Rejected > StyleProps and StyleClassProps should be merged to one interface > ---------------------------------------------------------------- > > Key: RF-13244 > URL: https://issues.jboss.org/browse/RF-13244 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > It doesn't make sense to have several style-realted interface since style and styleClass appears togetger. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13216: ------------------------------------ [~tkonishi] can we close this issue? > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Labels: gss > Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > <h:body title="page 1"> > <a4j:outputPanel id="myPanel"> > <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}"> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/> > </h:form> > </rich:popupPanel> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/> > </h:form> > </a4j:outputPanel> > </h:body> > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13216: ------------------------------- Labels: gss waiting_on_user (was: gss) > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Labels: gss, waiting_on_user > Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > <h:body title="page 1"> > <a4j:outputPanel id="myPanel"> > <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}"> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/> > </h:form> > </rich:popupPanel> > <h:form> > <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/> > </h:form> > </a4j:outputPanel> > </h:body> > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13210) Move RichFaces resources from META-INF/resources/ to org.richfaces library

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13210: ---------------------------------- Assignee: Lukáš Fryč [~lfryc] is this now out of date? > Move RichFaces resources from META-INF/resources/ to org.richfaces library > -------------------------------------------------------------------------- > > Key: RF-13210 > URL: https://issues.jboss.org/browse/RF-13210 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > -- 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, 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 November 2013