From issues at jboss.org Mon Apr 14 07:40:34 2014 Content-Type: multipart/mixed; boundary="===============9154139253036065962==" MIME-Version: 1.0 From: Michal Petrov (JIRA) To: richfaces-issues at lists.jboss.org Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost Date: Mon, 14 Apr 2014 07:40:34 -0400 Message-ID: In-Reply-To: JIRA.12538133.1397472858000@jira02.app.mwc.hst.phx2.redhat.com --===============9154139253036065962== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/RF-13605?page=3Dcom.atlassian.jira.pl= ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12961570#com= ment-12961570 ] = Michal Petrov commented on RF-13605: ------------------------------------ Like [~avijra] said in the mail, I'm not sure this should be considered a b= ug. What happens is that the onblur triggers a rerender and so a part of DO= M, button included, is replaced. The click on the original button either ne= ver happens to begin with, or is not executed since the button doesn't exis= t any more. Given that the ajax request may take a while to come back I ass= ume the click might still register sometimes. {code} {code} As far as I understand this should do essentially the same thing, albeit wi= thout ajax. The click doesn't trigger either. = > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) = > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > > Clicking on the submit button of a form containing input elements with va= luechange event listeners triggers only the execution of the event listener= s of the corresponding input elements, but the button click event apparentl= y gets lost and the form isn't actually being submitted. The user has to cl= ick on the button again to finally submit it. Explicitly setting the reques= tDelay of an associated a4j:queue to say 200ms for all events seems to pres= erve the click event and the form gets submitted as expected in our specifi= c test environment. This isn't a generally acceptable workaround though, as= it introduces redundant global delay and hardly preserves the click event = reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file con= taining a minimal JSF application with a simple RichFaces-enabled form whic= h reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira --===============9154139253036065962==--