ICEfaces
  1. ICEfaces
  2. ICE-5747

Compat Showcase: Tree demo in FF3.6

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Alpha3
          • Fix Version/s: 2.0-Alpha3
          • Component/s: Sample Apps
          • Labels:
            None
          • Environment:
            FF3.6
          • Assignee Priority:
            P1

            Description

            Compat Showcase Tree demo:

            In FF3.6, clicking the <Move Up> or <Move Down> button once will actually make the name moving over two rows instead of one.

            Using Chrome, it works correctly (only moves one row at a time).

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              yip.ng added a comment -

              Nothing wrong with the tree. It's the button. Every click triggers the button decode() twice. Seems every click generates 2 posts. There is also a bridge JS error. See video at: http://screencast.com/t/MWFjMWM0N

              Show
              yip.ng added a comment - Nothing wrong with the tree. It's the button. Every click triggers the button decode() twice. Seems every click generates 2 posts. There is also a bridge JS error. See video at: http://screencast.com/t/MWFjMWM0N
              Hide
              Permalink
              Mircea Toma added a comment -

              For some reason unknown to me, FF doesn't set 'form' variable when button's onclick event listener is invoked. This causes the resetHiddenFieldsFor() function to fail (throw error) and eventually the listener code fails to return. The listener normally returns 'false' to block the event from propagating to the form element which would cause another submit. Because the listener code fails we see the double submit.

              The fix introduced infers the form from the submitting element in case 'form' parameter is null.

              Show
              Mircea Toma added a comment - For some reason unknown to me, FF doesn't set 'form' variable when button's onclick event listener is invoked. This causes the resetHiddenFieldsFor() function to fail (throw error) and eventually the listener code fails to return. The listener normally returns 'false' to block the event from propagating to the form element which would cause another submit. Because the listener code fails we see the double submit. The fix introduced infers the form from the submitting element in case 'form' parameter is null.
              Hide
              Permalink
              Joanne Bai added a comment -

              verified successfully using icefaces-2.0.0-alpha3

              Show
              Joanne Bai added a comment - verified successfully using icefaces-2.0.0-alpha3

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Joanne Bai
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: