ICEfaces
  1. ICEfaces
  2. ICE-9718

Support ace:dataTable pinned columns feature in combination with multiple row column headers

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 4.3
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 4

      Description

      The initial implementation of the pinnable columns feature in ace:dataTable does not work well when used in conjunction with multiple column header rows. This JIRA is to add full support for using pinned columns with multiple row headers.

        Issue Links

          Activity

          Ken Fyten created issue -
          Ken Fyten made changes -
          Field Original Value New Value
          Link This issue blocks ICE-8888 [ ICE-8888 ]
          Ken Fyten made changes -
          Fix Version/s 4.1 [ 11375 ]
          Ken Fyten made changes -
          Fix Version/s 4.2 [ 12870 ]
          Fix Version/s 4.1 [ 11375 ]
          Ken Fyten made changes -
          Fix Version/s EE-4.2.0.GA [ 13071 ]
          Fix Version/s 4.2 [ 12870 ]
          Ken Fyten made changes -
          Fix Version/s 4.3 [ 13096 ]
          Fix Version/s EE-4.2.0.GA [ 13071 ]
          Ken Fyten made changes -
          Assignee Arturo Zambrano [ artzambrano ]
          Hide
          Arturo Zambrano added a comment -

          Because of the complexity of the column pinning and multiple row header features and the styling requirements of each of them, it's not feasible to make both of these features work together. More specifically, the column pinning feature is based on adding some dynamic CSS to re-position all the cells of a column, plus header and footer, at the left of the table, without having to add additional nodes. In the case of multiple row headers, parent header cells in the top rows can have a variable column span, so it would result in various types of conflicts trying to move those header cells to the left, especially when other unpinned leaf header cells have those same parents cells above them. There would be many possible cases and scenarios to cover, that it would require some considerable effort and time to make this work perfectly. Most likely, in order to support these features together, we would have to completely change the current tried and tested approach to column pinning to something more complex that would involve creating nodes dynamically.

          Show
          Arturo Zambrano added a comment - Because of the complexity of the column pinning and multiple row header features and the styling requirements of each of them, it's not feasible to make both of these features work together. More specifically, the column pinning feature is based on adding some dynamic CSS to re-position all the cells of a column, plus header and footer, at the left of the table, without having to add additional nodes. In the case of multiple row headers, parent header cells in the top rows can have a variable column span, so it would result in various types of conflicts trying to move those header cells to the left, especially when other unpinned leaf header cells have those same parents cells above them. There would be many possible cases and scenarios to cover, that it would require some considerable effort and time to make this work perfectly. Most likely, in order to support these features together, we would have to completely change the current tried and tested approach to column pinning to something more complex that would involve creating nodes dynamically.
          Arturo Zambrano made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Won't Fix [ 2 ]
          Ken Fyten made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved: