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 reassigned RF-13340: ---------------------------------- Assignee: Jiří Štefek (was: Brian Leathem) I suspect this is out of date with recent fixes. [~jstefek] can you please confirm? > 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 > > > 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-13339) orderingList: ordered values are reset after submit

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13339. -------------------------------- Fix Version/s: (was: 5.0.0.Alpha2) Resolution: Out of Date This works with the latest master. > orderingList: ordered values are reset after submit > --------------------------------------------------- > > Key: RF-13339 > URL: https://issues.jboss.org/browse/RF-13339 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Priority: Blocker > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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-13329) Delete old 4.x and below pickList and orderingList resources from RF5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13329. -------------------------------- Resolution: Done > Delete old 4.x and below pickList and orderingList resources from RF5 > --------------------------------------------------------------------- > > Key: RF-13329 > URL: https://issues.jboss.org/browse/RF-13329 > Project: RichFaces > Issue Type: Task > 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 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}. > I mean {{.js}} and {{.ecss}} files from this folder: > https://github.com/richfaces/richfaces/tree/master/framework/src/main/res... -- 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 alexey plotnikov (JIRA)

alexey plotnikov created RF-13349: ------------------------------------- Summary: 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 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

[JBoss JIRA] (RF-13329) Delete old 4.x and below pickList and orderingList resources from RF5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13329: ---------------------------------- Assignee: Brian Leathem > Delete old 4.x and below pickList and orderingList resources from RF5 > --------------------------------------------------------------------- > > Key: RF-13329 > URL: https://issues.jboss.org/browse/RF-13329 > Project: RichFaces > Issue Type: Task > 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 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}. > I mean {{.js}} and {{.ecss}} files from this folder: > https://github.com/richfaces/richfaces/tree/master/framework/src/main/res... -- 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-13325) pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13325. -------------------------------- Fix Version/s: (was: 5.0.0.Alpha2) Resolution: Rejected > pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element > ---------------------------------------------------------------------------------------------------- > > Key: RF-13325 > URL: https://issues.jboss.org/browse/RF-13325 > 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 > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself. > I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not. -- 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-13330) RichFaces.jQuery should be used in CDK templates instead of $

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13330: ---------------------------------- Assignee: Brian Leathem > RichFaces.jQuery should be used in CDK templates instead of $ > ------------------------------------------------------------- > > Key: RF-13330 > URL: https://issues.jboss.org/browse/RF-13330 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery. > https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f34... > https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f34... -- 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-13329) Delete old 4.x and below pickList and orderingList resources from RF5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13329: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 5 > Delete old 4.x and below pickList and orderingList resources from RF5 > --------------------------------------------------------------------- > > Key: RF-13329 > URL: https://issues.jboss.org/browse/RF-13329 > Project: RichFaces > Issue Type: Task > 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 > > Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}. > I mean {{.js}} and {{.ecss}} files from this folder: > https://github.com/richfaces/richfaces/tree/master/framework/src/main/res... -- 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-13339) orderingList: ordered values are reset after submit

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13339: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 5 > orderingList: ordered values are reset after submit > --------------------------------------------------- > > Key: RF-13339 > URL: https://issues.jboss.org/browse/RF-13339 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Assignee: Brian Leathem > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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-13325) pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13325: ------------------------------------ Let's leave it for a user to request the feature. > pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element > ---------------------------------------------------------------------------------------------------- > > Key: RF-13325 > URL: https://issues.jboss.org/browse/RF-13325 > 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 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself. > I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not. -- 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