ICEfaces
  1. ICEfaces
  2. ICE-11276

ace:list issue when reordering a selected item while using ajax

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.2
    • Fix Version/s: EE-4.2.0.GA
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ICEfaces4 trunk r 51364
      Browsers: all
      Server: Tomcat7
    • Assignee Priority:
      P2

      Description

      ICEfaces4 trunk r51364/all browsers
      On Showcase > Exporting: Block Objects demo, after selecting an item and then dragging it to a different position, the item is multiplied, see attached Capture1.PNG.
      Otherwise, the exported file contains the correct number of items.

      According to Art, the issue above is a bug in ace:list when reordering a selected item while using ajax. It's only an issue on the client side; the model in the server is unaffected.

        Activity

        Hide
        Arturo Zambrano added a comment -

        r51390: added flags to prevent ajax submits when programmatically calling deselectAll() and addSelectedItem() to update the list's selection state when reordering items

        Some methods that handled selections and deselections are necessary to be called when reordering items to update the selection state of the list with the new order. The problem was that these methods are the same methods invoked when the user selects or deselects an item, which were firing their respective ajax events even if they weren't initiated by the user. This issue was fixed by preventing those ajax events that aren't initiated by the user, so that only the selection/deselection logic is applied.

        Show
        Arturo Zambrano added a comment - r51390: added flags to prevent ajax submits when programmatically calling deselectAll() and addSelectedItem() to update the list's selection state when reordering items Some methods that handled selections and deselections are necessary to be called when reordering items to update the selection state of the list with the new order. The problem was that these methods are the same methods invoked when the user selects or deselects an item, which were firing their respective ajax events even if they weren't initiated by the user. This issue was fixed by preventing those ajax events that aren't initiated by the user, so that only the selection/deselection logic is applied.

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Carmen Cristurean
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: