[ 
https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matej Novotny updated RF-13711:
-------------------------------

    Affects Version/s: 4.3.8


> a4j:ajax status does not work as expected
> -----------------------------------------
>
>                 Key: RF-13711
>                 URL: https://issues.jboss.org/browse/RF-13711
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.3.7, 4.3.8
>         Environment: IE8, Mozilla Firefox 30
>            Reporter: Evgeny Mironenko
>            Assignee: Matej Novotny
>
> Status attribute for {{a4j:ajax}} does not work as expected. 
> I tried to create simple project with content:
> {code:title=index.xhtml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> <html xmlns="http://www.w3.org/1999/xhtml";
>     xmlns:h="http://java.sun.com/jsf/html";
>     xmlns:a4j="http://richfaces.org/a4j";>
>     <h:head>
>     </h:head>
>     <h:body>
>         <a4j:status id="progress" onstart="console.log('start')"
>             onstop="console.log('stop')"/>
>         <div id="content">
>             <h:form>
>                 <h:commandButton value="Click">
>                     <a4j:ajax event="click" status="progress" 
> listener="#{testBean.invoke}"/>
>                 </h:commandButton>
>             </h:form>
>         </div>
>     </h:body>
> </html>
> {code}
> It did not work for me. I do not see any log messages in the console. 
> As workaround I can use the {{render}} attribute instead of {{status}}, but 
> we use it for another goals, am I right?



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
_______________________________________________
richfaces-issues mailing list
richfaces-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to