ICEfaces
  1. ICEfaces
  2. ICE-7028

Grouped Column Header Feature Combination Incompatibilities

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1-Beta2
    • Fix Version/s: 3.0.RC1, 3.0
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ICE 2.1, JSF2, Tomcat6
    • Assignee Priority:
      P3

      Description

      JIRA covers problems that would occur through the combination of grouped headers with other features.

      For example, major problems have already been observed in combination with: Dynamic Columns, Sorting, Filtering and Scrolling layout.

        Issue Links

          Activity

          Hide
          Nils Lundquist added a comment -

          Rev. 24978

          Many changes were carried out to support robust sizing of grouped headers columns during scrolling layout.

          This included changes to the renderer to support resizable body columns.
          That in turn included changes to JS selectors, so that they would be robust enough to find their targets with or without the changes made to the renderer.

          Show
          Nils Lundquist added a comment - Rev. 24978 Many changes were carried out to support robust sizing of grouped headers columns during scrolling layout. This included changes to the renderer to support resizable body columns. That in turn included changes to JS selectors, so that they would be robust enough to find their targets with or without the changes made to the renderer.
          Hide
          Nils Lundquist added a comment -

          Just resolved an issue with sorting.

          Produced by having sortBy="#

          {item.property}

          " on several columns within a grouped column header. Multi column sorting wasn't possible, and sort priorities were always interpreted as 1.

          This was due to use of table.getColumns() in sort decode. getColumns() returns the table body columns, where the case required the set of columns defined in the header group.

          Show
          Nils Lundquist added a comment - Just resolved an issue with sorting. Produced by having sortBy="# {item.property} " on several columns within a grouped column header. Multi column sorting wasn't possible, and sort priorities were always interpreted as 1. This was due to use of table.getColumns() in sort decode. getColumns() returns the table body columns, where the case required the set of columns defined in the header group.
          Hide
          Nils Lundquist added a comment -

          Tested other scenarios and found they work at the moment.

          Show
          Nils Lundquist added a comment - Tested other scenarios and found they work at the moment.

            People

            • Assignee:
              Nils Lundquist
              Reporter:
              Nils Lundquist
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: