rich:status - when onerror changed by partial refresh, it's definition is ignored for first error request --------------------------------------------------------------------------------------------------------- Key: RF-9118 URL: https://jira.jboss.org/browse/RF-9118 Project: RichFaces Issue Type: Bug Security Level: Public(Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Milestone1 Environment: Apache Tomcat 6.0.26 OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1~9.10.1) Metamer Application rev. 18834 ( https://svn.jboss.org/repos/richfaces/modules/tests/metamer/trunk/applica... ) Reporter: Lukas Fryc Assignee: Nick Belaevski Fix For: 4.0.0.Milestone2 Steps to reproduce: 1. open http://localhost:8080/metamer/faces/components/a4jStatus/instantAttribute... 2. type in "alert('error1') into "onerror" input and hit Tab button (trigger change event) (the partial refresh will cause rerendering of the "commonGrid" component containing the "status") 3. hit "Send Ajax Requeswt Causing Error" button ERROR: no alert is triggered and status is stating "STOP" instead of "ERROR" 4. hit button again OK: alert is triggered stating "error1" and also status is stating "ERROR" This is at least unexpected behaviour and also doesn't match the principle what is used in case of other event listeners, especially "onsuccess".

rich:status - when onerror changed by partial refresh, it's definition is ignored for first error request --------------------------------------------------------------------------------------------------------- Key: RF-9118 URL: https://jira.jboss.org/browse/RF-9118 Project: RichFaces Issue Type: Bug Security Level: Public(Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Milestone1 Environment: Apache Tomcat 6.0.26 OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1~9.10.1) Metamer Application rev. 18834 ( https://svn.jboss.org/repos/richfaces/modules/tests/metamer/trunk/applica... ) Reporter: Lukas Fryc Assignee: Nick Belaevski Fix For: 4.0.0.Milestone2 Steps to reproduce: 1. open http://localhost:8080/metamer/faces/components/a4jStatus/instantAttribute... 2. type in "alert('error1') into "onerror" input and hit Tab button (trigger change event) (the partial refresh will cause rerendering of the "commonGrid" component containing the "status") 3. hit "Send Ajax Requeswt Causing Error" button ERROR: no alert is triggered and status is stating "STOP" instead of "ERROR" 4. hit button again OK: alert is triggered stating "error1" and also status is stating "ERROR" This is at least unexpected behaviour and also doesn't match the principle what is used in case of other event listeners, especially "onsuccess".

rich:status - when onerror changed by partial refresh, it's definition is ignored for first error request --------------------------------------------------------------------------------------------------------- Key: RF-9118 URL: https://issues.jboss.org/browse/RF-9118 Project: RichFaces Issue Type: Bug Security Level: Public(Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Milestone1, 4.1.0.Milestone1 Environment: Apache Tomcat 6.0.26 OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1~9.10.1) Metamer Application rev. 18834 ( https://svn.jboss.org/repos/richfaces/modules/tests/metamer/trunk/applica... ) Reporter: Lukáš Fryč Assignee: Jay Balunas Priority: Critical Labels: ci_issue, metamer-ftest-tracked Fix For: 4.0.0.Milestone2 Steps to reproduce: 1. open http://localhost:8080/metamer/faces/components/a4jStatus/instantAttribute... 2. type in "alert('error1') into "onerror" input and hit Tab button (trigger change event) (the partial refresh will cause rerendering of the "commonGrid" component containing the "status") 3. hit "Send Ajax Requeswt Causing Error" button ERROR: no alert is triggered and status is stating "STOP" instead of "ERROR" 4. hit button again OK: alert is triggered stating "error1" and also status is stating "ERROR" This is at least unexpected behaviour and also doesn't match the principle what is used in case of other event listeners, especially "onsuccess".

rich:status - when onerror changed by partial refresh, it's definition is ignored for first error request --------------------------------------------------------------------------------------------------------- Key: RF-9118 URL: https://issues.jboss.org/browse/RF-9118 Project: RichFaces Issue Type: Bug Security Level: Public(Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Milestone1, 4.1.0.Milestone1 Environment: Apache Tomcat 6.0.26 OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1~9.10.1) Metamer Application rev. 18834 ( https://svn.jboss.org/repos/richfaces/modules/tests/metamer/trunk/applica... ) Reporter: Lukáš Fryč Assignee: Jay Balunas Priority: Critical Labels: ci_issue, metamer-ftest-tracked Fix For: 4.Future Steps to reproduce: 1. open http://localhost:8080/metamer/faces/components/a4jStatus/instantAttribute... 2. type in "alert('error1') into "onerror" input and hit Tab button (trigger change event) (the partial refresh will cause rerendering of the "commonGrid" component containing the "status") 3. hit "Send Ajax Requeswt Causing Error" button ERROR: no alert is triggered and status is stating "STOP" instead of "ERROR" 4. hit button again OK: alert is triggered stating "error1" and also status is stating "ERROR" This is at least unexpected behaviour and also doesn't match the principle what is used in case of other event listeners, especially "onsuccess".