October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13272) Manage the RichFaces jquery.js dependency with RichWidgets

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13272?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13272: ------------------------------------ RichFaces 4.5 uses jQuery from RichFaces core (now part of RichFaces 5 framework). With this update we will need to be sure we don't break the 4.5 UI components. > Manage the RichFaces jquery.js dependency with RichWidgets > ---------------------------------------------------------- > > Key: RF-13272 > URL: https://issues.jboss.org/browse/RF-13272 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The jQuery UI dependencies are currently set within RichWidgets and copied into RichFaces via a grunt task. > The jQuery.js dpendency should be similarly managed. While making this change, the jQuery.js library should be changed to _com.jquery_. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13272) Manage the RichFaces jquery.js dependency with RichWidgets

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13272?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13272: ------------------------------------ RichFaces currently uses JQuery 1.8.3: https://github.com/richfaces/richfaces/blob/master/framework/src/main/res... RichWidgets currently uses jQuery 1.9.0: https://github.com/richwidgets/richwidgets/blob/master/bower.json#L5 >From the jQuery Core 1.9 Upgrade Guide: http://jquery.com/upgrade-guide/1.9/ {quote} jQuery 1.9 removes or modifies several APIs that behaved inconsistently or inefficiently in the past. {quote} We will need to include the jQuery Migrate plugin and use it to collect and correct deprecation warnings: https://github.com/jquery/jquery-migrate/ {quote} The uncompressed development version of the jQuery Migrate plugin includes console log output to warn when specific deprecated and/or removed features are being used. {quote} > Manage the RichFaces jquery.js dependency with RichWidgets > ---------------------------------------------------------- > > Key: RF-13272 > URL: https://issues.jboss.org/browse/RF-13272 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The jQuery UI dependencies are currently set within RichWidgets and copied into RichFaces via a grunt task. > The jQuery.js dpendency should be similarly managed. While making this change, the jQuery.js library should be changed to _com.jquery_. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13275) Replace #{toScriptArgs(options)} with #{options.toJson()}

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13275?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13275: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Replace #{toScriptArgs(options)} with #{options.toJson()} > ---------------------------------------------------------- > > Key: RF-13275 > URL: https://issues.jboss.org/browse/RF-13275 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: cdk, core > Affects Versions: 4.5.0.Alpha1, 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha3 > > > We should rewrite <cdk:scriptObject> to generate Map which exposes > {{#toJson()}} function, that works as {{ScriptUtils.toScript}}. > This will overcome defficiencies of {{#{toScriptArgs(options)}} mentioned in RF-12593. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-13180. ----------------------------- Resolution: Rejected I'm rejecting this issue as we discussed it offline and as Brian pointed earlier, we should stick with current semantics which are inherited from HTML inputs themselves. Please review the log and remove fixVersion before closing. > Autocomplete: ajax doesn't work with change event > ------------------------------------------------- > > Key: RF-13180 > URL: https://issues.jboss.org/browse/RF-13180 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > # select Alabama > result: > * ajax request is not fired > * output is not updated > * when "change" event in r:ajax is changed to "blur", the use-case 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13180: --------------------------------- I have opened a mailing list thread to discuss deficiencies of {{value}} event. > Autocomplete: ajax doesn't work with change event > ------------------------------------------------- > > Key: RF-13180 > URL: https://issues.jboss.org/browse/RF-13180 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > # select Alabama > result: > * ajax request is not fired > * output is not updated > * when "change" event in r:ajax is changed to "blur", the use-case 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13180 at 10/21/13 6:11 AM: ----------------------------------------------------------- [~ppitonak] I have just tried (2) in Metamer and components-demo and when I select an option and then click to the document body (anywhere else), the AJAX request is triggered and it states "Your Selection: Alabama" I can demonstrate it to you if necessary. I also belivies that this is what test addresses (1). was (Author: lfryc): [~ppitonak] I have just tried (2) in Metamer and components-demo and when I select an option and then click to the document body (anywhere else), the AJAX request is triggered and it states "Your Selection: Alabama" I can demonstrate it to you if necessary. > Autocomplete: ajax doesn't work with change event > ------------------------------------------------- > > Key: RF-13180 > URL: https://issues.jboss.org/browse/RF-13180 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > # select Alabama > result: > * ajax request is not fired > * output is not updated > * when "change" event in r:ajax is changed to "blur", the use-case 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13180: --------------------------------- (3) This latest VDL online is out of date, look at the component source: https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... > Autocomplete: ajax doesn't work with change event > ------------------------------------------------- > > Key: RF-13180 > URL: https://issues.jboss.org/browse/RF-13180 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > # select Alabama > result: > * ajax request is not fired > * output is not updated > * when "change" event in r:ajax is changed to "blur", the use-case 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13180 at 10/21/13 6:10 AM: ----------------------------------------------------------- [~ppitonak] I have just tried (2) in Metamer and components-demo and when I select an option and then click to the document body (anywhere else), the AJAX request is triggered and it states "Your Selection: Alabama" I can demonstrate it to you if necessary. was (Author: lfryc): [~ppitonak] I have just tried (1) in Metamer and components-demo and when I select an option and then click to the document body (anywhere else), the AJAX request is triggered and it states "Your Selection: Alabama" I can demonstrate it to you if necessary. > Autocomplete: ajax doesn't work with change event > ------------------------------------------------- > > Key: RF-13180 > URL: https://issues.jboss.org/browse/RF-13180 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > # select Alabama > result: > * ajax request is not fired > * output is not updated > * when "change" event in r:ajax is changed to "blur", the use-case 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12593) RenderKitUtils.toScriptArgs() returns empty string when no not-null parameter provided

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12593?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12593. ----------------------------- Fix Version/s: (was: 5.0.0.Alpha2) Resolution: Rejected > RenderKitUtils.toScriptArgs() returns empty string when no not-null parameter provided > -------------------------------------------------------------------------------------- > > Key: RF-12593 > URL: https://issues.jboss.org/browse/RF-12593 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.0.M2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Minor > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The {{toScriptArgs(Object object)}} should always return JavaScript object: > {code:javascript} > { ... } > {code} > In case null object or no not-null parameter provided, empty object should be returned: > {code:javascript} > {} > {code} > Currently, it returns empty string {{""}} which is not handy if we expect JavaScript object as a return value. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12593) RenderKitUtils.toScriptArgs() returns empty string when no not-null parameter provided

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12593?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12593: --------------------------------- As we discussed offline, the original intention of {{toScriptArgs}} is different: * it suppose to generate function parameters so the fact it can return empty string is given from the fact, that it is usually intended to be placed directly to method invocations, such as: {code} new RichFaces.ui.Push(#{toScriptArgs(clientId, options)}); {code} but not assigning a value, such as: {code} var options = #{toScriptArgs(options)}; {code} We will address this issue in RF-13725. > RenderKitUtils.toScriptArgs() returns empty string when no not-null parameter provided > -------------------------------------------------------------------------------------- > > Key: RF-12593 > URL: https://issues.jboss.org/browse/RF-12593 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.0.M2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Minor > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The {{toScriptArgs(Object object)}} should always return JavaScript object: > {code:javascript} > { ... } > {code} > In case null object or no not-null parameter provided, empty object should be returned: > {code:javascript} > {} > {code} > Currently, it returns empty string {{""}} which is not handy if we expect JavaScript object as a return value. -- 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, 5 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 October 2013