March 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13574) Editor readonly mode

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13574?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13574: --------------------------------- Here is up to date documentation: https://rawgithub.com/richwidgets/richwidgets/dist/dist/demos/api/classes... > Editor readonly mode > -------------------- > > Key: RF-13574 > URL: https://issues.jboss.org/browse/RF-13574 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha4 > Environment: Wildfly, Firefox, Metamer (master branch) > Reporter: Matej Novotny > Fix For: 5.0.0.Alpha4 > > > With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer. > I checked the attributes editor should have, the bean where via which it is controlled and found no problems there. > I also tried creating editor with readonly='true' which does not work either. > One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere. > There is a test prepared for this: [testToolbar()|https://github.com/richfaces/richfaces-qa/blob/master/metam...] -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13574) Editor readonly mode

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13574?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13574: --------------------------------- I can see that the widget works fine: https://rawgithub.com/richwidgets/richwidgets/dist/dist/demos/input/edito... {code} $('#basic-editor').editor('readOnly', true); ... $('#basic-editor').editor('readOnly', false); {code} > Editor readonly mode > -------------------- > > Key: RF-13574 > URL: https://issues.jboss.org/browse/RF-13574 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha4 > Environment: Wildfly, Firefox, Metamer (master branch) > Reporter: Matej Novotny > Fix For: 5.0.0.Alpha4 > > > With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer. > I checked the attributes editor should have, the bean where via which it is controlled and found no problems there. > I also tried creating editor with readonly='true' which does not work either. > One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere. > There is a test prepared for this: [testToolbar()|https://github.com/richfaces/richfaces-qa/blob/master/metam...] -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13574) Editor readonly mode

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13574?page=com.atlassian.jira.plugin.s... ] Matej Novotny updated RF-13574: ------------------------------- Description: With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer. I checked the attributes editor should have, the bean where via which it is controlled and found no problems there. I also tried creating editor with readonly='true' which does not work either. One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere. There is a test prepared for this: [testToolbar()|https://github.com/richfaces/richfaces-qa/blob/master/metam...] was: With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer. I checked the attributes editor should have, the bean where via which it is controlled and found no problems there. I also tried creating editor with readonly='true' which does not work either. One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere. > Editor readonly mode > -------------------- > > Key: RF-13574 > URL: https://issues.jboss.org/browse/RF-13574 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha4 > Environment: Wildfly, Firefox, Metamer (master branch) > Reporter: Matej Novotny > Fix For: 5.0.0.Alpha4 > > > With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer. > I checked the attributes editor should have, the bean where via which it is controlled and found no problems there. > I also tried creating editor with readonly='true' which does not work either. > One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere. > There is a test prepared for this: [testToolbar()|https://github.com/richfaces/richfaces-qa/blob/master/metam...] -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13505: --------------------------------- Yes, we need to re-test it as CR1 did not contain the fix. > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.Alpha4 > > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13559) Backport RF-13018 (a4j:commandButton wrong actions performed) to RF 4

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13559?page=com.atlassian.jira.plugin.s... ] Michal Petrov resolved RF-13559. -------------------------------- Fix Version/s: 4.3.6 4.5.0.Alpha3 Resolution: Done > Backport RF-13018 (a4j:commandButton wrong actions performed) to RF 4 > --------------------------------------------------------------------- > > Key: RF-13559 > URL: https://issues.jboss.org/browse/RF-13559 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > Assignee: Michal Petrov > Fix For: 4.3.6, 4.5.0.Alpha3 > > > Backport fix for RF-13018 from RF 5 to RF 4. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue)

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13505: ---------------------------------- Please wait with incorporating! I am sorry but I accidentally tested on WildFly 8.0.0.CR1. I need to retest in Final. Will let you know the results. > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha4 > > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue)

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-13505: ----------------------------- Assignee: Juraj Húska (was: Lukáš Fryč) > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.Alpha4 > > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ] Michal Petrov resolved RF-13018. -------------------------------- Fix Version/s: 5.0.0.Alpha4 (was: 5-Tracking) Resolution: Done > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Fix For: 5.0.0.Alpha4 > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > <h:form id="testForm"> > <a4j:commandButton id="button1" type="button" value="Button 1" > action="#{richBean.function1}" /> > <a4j:commandButton id="button2" type="button" value="Button 2" > action="#{richBean.function2}" /> > </h:form> > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ] Michal Petrov commented on RF-13018: ------------------------------------ This was caused by JSF, when it parses the form before sending the AJAX request it treats the buttons as basic input fields and puts them in the query string (apparently this is according to/not against W3C spec). Since the default behaviour is to execute the entire form the decoder finds those ids and executes them. (In older version versions even @type="reset" are treated this way.) > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Fix For: 5-Tracking > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > <h:form id="testForm"> > <a4j:commandButton id="button1" type="button" value="Button 1" > action="#{richBean.function1}" /> > <a4j:commandButton id="button2" type="button" value="Button 2" > action="#{richBean.function2}" /> > </h:form> > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ] Michal Petrov reassigned RF-13018: ---------------------------------- Assignee: Michal Petrov (was: Brian Leathem) > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Fix For: 5-Tracking > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > <h:form id="testForm"> > <a4j:commandButton id="button1" type="button" value="Button 1" > action="#{richBean.function1}" /> > <a4j:commandButton id="button2" type="button" value="Button 2" > action="#{richBean.function2}" /> > </h:form> > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- 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

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2014