April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12907) render="@form" problem with a4jCommand Button

by Jean ANDRE (JIRA)

[ https://issues.jboss.org/browse/RF-12907?page=com.atlassian.jira.plugin.s... ] Jean ANDRE commented on RF-12907: --------------------------------- Yes of course. Does having a version with a CDI (Weld) from Glassfish will be ok ?... Preparing it in case. It easy to convert the application. See readme.txt file on NestebWeb folder. > render="@form" problem with a4jCommand Button > --------------------------------------------- > > Key: RF-12907 > URL: https://issues.jboss.org/browse/RF-12907 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.1 > Environment: JSF Mojarra 2.1.21 or 2.1.20 - Glassfish or WAS 8.0.0.x Servlet 3.0 or 2.5 > Reporter: Jean ANDRE > Priority: Blocker > Labels: waiting_on_user > Attachments: Nested-Spring-3.2.2.zip > > > Please see the report at: http://java.net/jira/browse/JAVASERVERFACES-2016 > It seems that that there is a problem with a4j button and the value of @form/render attribute. > The symptom we got is after refreshing the panel for building a list. Click on link form the result lisk does not trigger the action. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12876) Add "for" attribute to rich:focus

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12876?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12876: --------------------------------- Internally, the FocusManager API can be used > Add "for" attribute to rich:focus > --------------------------------- > > Key: RF-12876 > URL: https://issues.jboss.org/browse/RF-12876 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Sandbox version of focus component allowed to specify "focus" > for particular component. I'm missing this very much. > If we have single form with 2 popup panels each with single input then with rich:focus we cannot specify which input should be focused. > And when we open popup A then we want to have input in that popup to be focused, not the one in popup B. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12876) Add "for" attribute to rich:focus

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12876?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12876: --------------------------------- Thanks Bernard, this help will be really appreciate. > Add "for" attribute to rich:focus > --------------------------------- > > Key: RF-12876 > URL: https://issues.jboss.org/browse/RF-12876 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Sandbox version of focus component allowed to specify "focus" > for particular component. I'm missing this very much. > If we have single form with 2 popup panels each with single input then with rich:focus we cannot specify which input should be focused. > And when we open popup A then we want to have input in that popup to be focused, not the one in popup B. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12876) Add "for" attribute to rich:focus

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/RF-12876?page=com.atlassian.jira.plugin.s... ] Bernard Labno commented on RF-12876: ------------------------------------ I'll have time for this after May 5th. > Add "for" attribute to rich:focus > --------------------------------- > > Key: RF-12876 > URL: https://issues.jboss.org/browse/RF-12876 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Sandbox version of focus component allowed to specify "focus" > for particular component. I'm missing this very much. > If we have single form with 2 popup panels each with single input then with rich:focus we cannot specify which input should be focused. > And when we open popup A then we want to have input in that popup to be focused, not the one in popup B. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12876) Add "for" attribute to rich:focus

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12876?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12876: ---------------------------- Fix Version/s: 5-Tracking > Add "for" attribute to rich:focus > --------------------------------- > > Key: RF-12876 > URL: https://issues.jboss.org/browse/RF-12876 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Sandbox version of focus component allowed to specify "focus" > for particular component. I'm missing this very much. > If we have single form with 2 popup panels each with single input then with rich:focus we cannot specify which input should be focused. > And when we open popup A then we want to have input in that popup to be focused, not the one in popup B. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12876) Add "for" attribute to rich:focus

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12876?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12876: --------------------------------- That make sense, I would assign this as a feature request for 5.x, but we could make it part of 4.3.x releases in case you would create a patch. > Add "for" attribute to rich:focus > --------------------------------- > > Key: RF-12876 > URL: https://issues.jboss.org/browse/RF-12876 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > > Sandbox version of focus component allowed to specify "focus" > for particular component. I'm missing this very much. > If we have single form with 2 popup panels each with single input then with rich:focus we cannot specify which input should be focused. > And when we open popup A then we want to have input in that popup to be focused, not the one in popup B. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12833?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12833 at 4/15/13 6:55 AM: ---------------------------------------------------------- This patch doesn't fix the issue either - I would propose this change: {code} window.RichFaces = window.RichFaces || {}; RichFaces.jQuery = RichFaces.jQuery || jQuery; (function(jQuery, richfaces) { ... }(RichFaces.jQuery, RichFaces)); {code} This way, users can initialize {{RichFaces.jQuery}} prior processing of {{richfaces.js}} - it will cause RichFaces to grab any version of jQuery you require (e.g. "noConflicted" version): {code} var myJQuery = jQuery.noConflict(); ... RichFaces.jQuery = myJQuery; {code} was (Author: lfryc): This patch doesn't fix the issue either - I would propose this change: {code} window.RichFaces = window.RichFaces || {}; RichFaces.jQuery = RichFaces.jQuery || jQuery; (function(jQuery, richfaces) { ... }(RichFaces.jQuery, RichFaces)); {code} This way, users can initialize {{RichFaces.jQuery}} prior processing of {{richfaces.js}} - it will cause RichFaces to grab any version of jQuery you require (e.g. "noConflicted" version). > richfaces.js conflicts with prototype.js > ---------------------------------------- > > Key: RF-12833 > URL: https://issues.jboss.org/browse/RF-12833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.1 > Reporter: Mark Torres > Fix For: 5-Tracking > > > Getting some javascript errors on richfaces.js. > Upon inspection, it is using > (function(jQuery, richfaces) { > ... > instead of > (function($, richfaces) { > ... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12833?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12833: --------------------------------- This patch doesn't fix the issue either - I would propose this change: {code} window.RichFaces = window.RichFaces || {}; RichFaces.jQuery = RichFaces.jQuery || jQuery; (function(jQuery, richfaces) { ... }(RichFaces.jQuery, RichFaces)); {code} This way, users can initialize {{RichFaces.jQuery}} prior processing of {{richfaces.js}} - it will cause RichFaces to grab any version of jQuery you require (e.g. "noConflicted" version). > richfaces.js conflicts with prototype.js > ---------------------------------------- > > Key: RF-12833 > URL: https://issues.jboss.org/browse/RF-12833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.1 > Reporter: Mark Torres > Fix For: 5-Tracking > > > Getting some javascript errors on richfaces.js. > Upon inspection, it is using > (function(jQuery, richfaces) { > ... > instead of > (function($, richfaces) { > ... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12833?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12833 at 4/15/13 6:47 AM: ---------------------------------------------------------- For workaround, you can use the patched version of {{richfaces.js}} from the linked pull request. (Note that the patch isn't completely correct as of now). Use RichFaces Resource Mapping [1] to rewrite original {{richfaces.js}} with the file stored in your own application. [1] http://lukas.fryc.eu/blog/2012/02/re-routing-jsf-resource-requests-with.html was (Author: lfryc): For workaround, you can use the patched version of {{richfaces.js}} from the linked pull request. Use RichFaces Resource Mapping [1] to rewrite original {{richfaces.js}} with the file stored in your own application. [1] http://lukas.fryc.eu/blog/2012/02/re-routing-jsf-resource-requests-with.html > richfaces.js conflicts with prototype.js > ---------------------------------------- > > Key: RF-12833 > URL: https://issues.jboss.org/browse/RF-12833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.1 > Reporter: Mark Torres > Fix For: 5-Tracking > > > Getting some javascript errors on richfaces.js. > Upon inspection, it is using > (function(jQuery, richfaces) { > ... > instead of > (function($, richfaces) { > ... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12833?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12833 at 4/15/13 6:47 AM: ---------------------------------------------------------- For workaround, you can use the patched version of {{richfaces.js}} from the linked pull request. (Note that the patch isn't completely correct as of now, but it will work for you). Use RichFaces Resource Mapping [1] to rewrite original {{richfaces.js}} with the file stored in your own application. [1] http://lukas.fryc.eu/blog/2012/02/re-routing-jsf-resource-requests-with.html was (Author: lfryc): For workaround, you can use the patched version of {{richfaces.js}} from the linked pull request. (Note that the patch isn't completely correct as of now). Use RichFaces Resource Mapping [1] to rewrite original {{richfaces.js}} with the file stored in your own application. [1] http://lukas.fryc.eu/blog/2012/02/re-routing-jsf-resource-requests-with.html > richfaces.js conflicts with prototype.js > ---------------------------------------- > > Key: RF-12833 > URL: https://issues.jboss.org/browse/RF-12833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.1 > Reporter: Mark Torres > Fix For: 5-Tracking > > > Getting some javascript errors on richfaces.js. > Upon inspection, it is using > (function(jQuery, richfaces) { > ... > instead of > (function($, richfaces) { > ... -- 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, 11 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 April 2013