ICEfaces
  1. ICEfaces
  2. ICE-9781

ace:confirmationDialog - h:commandButton actionListener not called

          Details

          • Assignee Priority:
            P1
          • Salesforce Case Reference:

            Description

            An ace:confirmationDialog uses an h:commandButton that will hide the dialog and open a new ace:dialog via the onclick event. This commandButton also as an actionListener which is not called when the ace:dialog show() function is called. The dialog is displayed but no update is sent to the server.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Arran Mccullough added a comment -

              Attached test case to reproduce issue. NOTE: the icefaces ace jar file needs to be added to run war file.

              Steps:

              • Load welcomeICEfaces.jsf
              • Click the Continue button
              • Confirmation dialog is shown.
              • Clock the OK Button, dialog is hidden and processing dialog is shown. The server logs should show a comment "OK Action Called" but this is not the case.
              Show
              Arran Mccullough added a comment - Attached test case to reproduce issue. NOTE: the icefaces ace jar file needs to be added to run war file. Steps: Load welcomeICEfaces.jsf Click the Continue button Confirmation dialog is shown. Clock the OK Button, dialog is hidden and processing dialog is shown. The server logs should show a comment "OK Action Called" but this is not the case.
              Hide
              Permalink
              Arturo Zambrano added a comment -

              r39524: committed fix to 4.0 trunk
              r39525: committed fix to 3.3 EE maintenance branch

              For some unknown reason, calling the jQuery UI function jQuery.dialog('open'), inside the dialog component's show() function, was causing the button click event never to complete and thus no request was being sent to the server. This was fixed by putting the contents of the show function inside a timeout function with a minimal delay, just to allow the triggering event to complete quickly and perform the default action.

              Show
              Arturo Zambrano added a comment - r39524: committed fix to 4.0 trunk r39525: committed fix to 3.3 EE maintenance branch For some unknown reason, calling the jQuery UI function jQuery.dialog('open'), inside the dialog component's show() function, was causing the button click event never to complete and thus no request was being sent to the server. This was fixed by putting the contents of the show function inside a timeout function with a minimal delay, just to allow the triggering event to complete quickly and perform the default action.

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Arran Mccullough
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: