ICEfaces
  1. ICEfaces
  2. ICE-9406

REGRESSION: ace:tabSet nested inside ace:dataTable

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: EE-3.3.0.GA, 4.0.BETA
          • Fix Version/s: 4.0.BETA, 4.0
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            Tomcat6, IE8, FF 3.6, & 21, Chrome 27, trunk revision #36588
          • Assignee Priority:
            P1

            Description

            Page is reloading when clicking on a button "updatePushVal". Assuming page should not be refreshed. Tab is refreshing to an inactive state.
            Test shows (Actual value 'ui-state-default ui-corner-top' did not match 'ui-state-default ui-corner-top ui-state-active').
            Has passed testing on trunk and branch until trunk revision #36588, July 04/13.
            The last time it passed was revision #34850 icefaces-ee-3.3.0 GA, June 27/13.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Mircea Toma added a comment -

              Which test case I need to use to reproduce this issue?

              Show
              Mircea Toma added a comment - Which test case I need to use to reproduce this issue?
              Hide
              Permalink
              Liana Munroe added a comment -

              tabSet nested Data Table Client

              Show
              Liana Munroe added a comment - tabSet nested Data Table Client
              Hide
              Permalink
              Mircea Toma added a comment - - edited

              The issue is caused by how the submit capture is done, it seems that the inline scripts for submit capturing are all setup for the first form in the data table.

              The applied fix changes how the form form's client ID is acquired. Now it correctly acquires it during render phase so that right form is queried when UISeries is iterating through its children.

              Show
              Mircea Toma added a comment - - edited The issue is caused by how the submit capture is done, it seems that the inline scripts for submit capturing are all setup for the first form in the data table. The applied fix changes how the form form's client ID is acquired. Now it correctly acquires it during render phase so that right form is queried when UISeries is iterating through its children.

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Liana Munroe
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: