ICEfaces
  1. ICEfaces
  2. ICE-8780

ace:tabSet label facet ace:pushButton causes second submit

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.2
          • Fix Version/s: 3.3
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            All browsers

            Description


            In the QA tabSet test app, with page facet/serverSideFacets.xhtml the third tabPane uses an ace:pushButton in the label facet, and when it is clicked, it causes two submits, the first for the pushButton and the second for changing to that tabPane.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Mark Collette added a comment - - edited

              Initially I thought that the label facet might be missing functionality called toggleOnInput=false in other components, which is when a clickable area in a container component may contain other components, and those include input or command components, then the click on the input or command component should not cause the activation of the container's clickable area. But it turned out that this functionality was in place, it just had an oversight of not handling the ace:pushButton case, which is for the element to be of type 'button'. Other compat code, that provides similar functionality for ice:panelCollapsible and ice:rowSelector, was found to be similarly deficient, by code auditing. Both the ACE and ICE codes were fixed to handle 'button' elements.
              icefaces3 trunk
              Subversion 32217

              Show
              Mark Collette added a comment - - edited Initially I thought that the label facet might be missing functionality called toggleOnInput=false in other components, which is when a clickable area in a container component may contain other components, and those include input or command components, then the click on the input or command component should not cause the activation of the container's clickable area. But it turned out that this functionality was in place, it just had an oversight of not handling the ace:pushButton case, which is for the element to be of type 'button'. Other compat code, that provides similar functionality for ice:panelCollapsible and ice:rowSelector, was found to be similarly deficient, by code auditing. Both the ACE and ICE codes were fixed to handle 'button' elements. icefaces3 trunk Subversion 32217
              Hide
              Permalink
              Mark Collette added a comment - - edited

              Assignee: Mark Collette
              Resolution: Fixed

              Show
              Mark Collette added a comment - - edited Assignee: Mark Collette Resolution: Fixed

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Mark Collette
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: