November 2013 - richfaces-issues - Jboss List Archives

[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 commented on RF-13344: ------------------------------------ See the discussion in RF-13346. > 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 > > {{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-13345) FileUpload: behaves incorrectly when placed in ajax rendered outputPanel

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13345?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13345: ------------------------------- Fix Version/s: 5-Tracking > FileUpload: behaves incorrectly when placed in ajax rendered outputPanel > ------------------------------------------------------------------------ > > Key: RF-13345 > URL: https://issues.jboss.org/browse/RF-13345 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Environment: EAP 6.1 > Chrome 30, Firefox 22 > Reporter: Jiří Štefek > Fix For: 5-Tracking > > Attachments: RF-13345-RF4-reproducer.zip, RF-13345-RF5-reproducer.zip > > > When fileUpload is placed in ajaxRendered outputPanel, just like this: > {code} > <a4j:outputPanel ajaxRendered="true"> > <rich:fileUpload fileUploadListener="#{richBean.listener}"/> > </a4j:outputPanel> > {code} > then it behaves incorrectly. > With RF 5: > the list of uploaded/to upload files is reset after each upload. > With RF 4: > * cannot manipulate with item(s) which was firstly uploaded > * the upload button is not rendered after first upload performed, but you can still add files and manipulate with them (delete them) -- 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: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > 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 > > > {{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-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 commented on RF-13346: ------------------------------------ While in [#75](https://github.com/richwidgets/richwidgets/issues/75#issuecomment-27821682) we agreed to follow the CSS behaviour and have: # Integer values default to px units # String values require units However, as [~michpetrov] pointed out, all facelet attribute values are strings, and so the unit is always required. While I don't advocate changing the RichWidget behaviour, I do feel we can safely add units in either the js bridge, or in the Renderer. I suspect it is most _clean_ to intercept the option in the bridge and add the units if they are missing. > 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 > > {{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-13347) pickList: switchByDblClick does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13347. -------------------------------- Resolution: Done > pickList: switchByDblClick does not work > ---------------------------------------- > > Key: RF-13347 > URL: https://issues.jboss.org/browse/RF-13347 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > > Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work. > Note that {{switchByClick}} works as expected. > It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works). -- 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-13347) pickList: switchByDblClick does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13347: ---------------------------------- Assignee: Brian Leathem > pickList: switchByDblClick does not work > ---------------------------------------- > > Key: RF-13347 > URL: https://issues.jboss.org/browse/RF-13347 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Brian Leathem > > Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work. > Note that {{switchByClick}} works as expected. > It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works). -- 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-13347) pickList: switchByDblClick does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13347: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > pickList: switchByDblClick does not work > ---------------------------------------- > > Key: RF-13347 > URL: https://issues.jboss.org/browse/RF-13347 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work. > Note that {{switchByClick}} works as expected. > It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works). -- 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-13347) pickList: switchByDblClick does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13347: ------------------------------------ It does not work because the default value in the component is true: {code} @Attribute(defaultValue = "true") public abstract boolean isSwitchByDblClick(); {code} The cdk does not set the option value if it is equal to the default value. In this case the default value in the component does not match the default value in the widget. I'll change the default in the widget to match. I will change the default value in the widget to match. > pickList: switchByDblClick does not work > ---------------------------------------- > > Key: RF-13347 > URL: https://issues.jboss.org/browse/RF-13347 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > > Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work. > Note that {{switchByClick}} works as expected. > It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works). -- 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-13348) pickList - columnClass attribute behaves differently than in RF4

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13348: ------------------------------------ Good question [~jhuska]. We have a conflict of compatibilities here. To be compatible with RF 4, or compatible with JSF. Would you mind raising this for discussion on richfaces-dev? We'll hash it out there, then come back and update this issue. > pickList - columnClass attribute behaves differently than in RF4 > ---------------------------------------------------------------- > > Key: RF-13348 > URL: https://issues.jboss.org/browse/RF-13348 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > > {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*: > Suppose a {{pickList}}, which items consist from _three_ columns. > * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}} > * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected > In *RF4*, it was different though: > * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc: > bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored. > The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ? -- 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-13349) a4j:queue must be first child for rich:autocomplete

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13349: ---------------------------------- Assignee: Pavol Pitonak QE, please verify > a4j:queue must be first child for rich:autocomplete > --------------------------------------------------- > > Key: RF-13349 > URL: https://issues.jboss.org/browse/RF-13349 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: alexey plotnikov > Assignee: Pavol Pitonak > > All described here https://community.jboss.org/message/845845 but i'll repeat. > In this example: > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > </rich:autocomplete> > {code} > a4j:queue - is *ignored!* > But here > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > </rich:autocomplete> > {code} > a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete. > For another components a4j:queue can be any child(first or last). > For example this code: > {code} > <h:selectOneMenu value="#{agentMenuMassList.menuProfile}"> > <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/> > <s:convertEntity/> > <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/> > <a4j:queue requestDelay="5000" /> > </h:selectOneMenu> > {code} > *not* ignoring a4j:queue -- 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