[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ] Matej Novotny commented on RF-13711: ------------------------------------ Alright I made a little bit of research on this because I found out we have this kind of usage in [Showcase|http://showcase.richfaces.org/richfaces/component-sample.jsf?dem...] and also we have similar use case in Metamer. So here are the results... What matters is, whether you have {{status}} attribute set or not. I will use following code snippet to explain in better. {code:xml} <h:form> <a4j:status id="progress" onstart="console.log('start')" onstop="console.log('stop')" /> <h:commandButton value="Click"> <a4j:ajax event="click" status="progress" /> <!-- not working --> </h:commandButton> <h:commandButton value="ClickMe2"> <a4j:ajax event="click" /> <!-- working --> </h:commandButton> </h:form> {code} The first button with attached ajax behavior has status set. This button *will not work*. This behaviour is IMHO a bug. The other button, however, *will work*. (Too see why a4j:status affects components which do not specifically use status attribute see [documentation|http://docs.jboss.org/richfaces/latest_4_3_X/Component_Refe...]). This is a correct solution but with more complex page, a4j:status might react on more requests than intended. But still I think this can be considered a workaround until we investigate further. Using a4j:commandButton instead of h:commandButton behaves equally. Also I made a mistake placing the reproducer in a4j:ajax instead of a4j:status, I will move and also alter the reproducer accordingly to my findings. I will update the issue information as well. [~rustock0] you can try the workaround I suggested, it might fit your needs better. -- This message was sent by Atlassian JIRA (v6.2.6#6264)