ICEfaces
  1. ICEfaces
  2. ICE-7889

ace:dataTable - Stacked column hr tag shows in footer

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: EE-3.0.0.BETA
    • Fix Version/s: 3.1
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ICEfaces EE 3.0 BETA 09032012
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      Using the following CSS style class override removed the unwanted <hr> tag:

      .ui-datatable tfoot td hr {
          display: none;
      }
      Show
      Using the following CSS style class override removed the unwanted <hr> tag: .ui-datatable tfoot td hr {     display: none; }

      Description

      When defining a footer section for a column and also using stacked columns the <hr> tag that is rendered for the stacked columns gets applied to the footer section. The footer is part of a different column than the ones that are stacked.

        Activity

        Hide
        Nils Lundquist added a comment - - edited

        In the screenshot above the presence of the HR is exacerbated by the missing borders that have now been solved in a recent JIRA.

        Look ahead calculation of null footer values to determine the presence of the hr tag is expensive for a subjective styling decision. I suggest using styling wherever possible to disable the visibility of hr tag. If this not possible in your scenario due to insufficient specificity of IDs etc. in the footer, this issue should be reopened to add the necessary unique identifiers to footer cells.

        Show
        Nils Lundquist added a comment - - edited In the screenshot above the presence of the HR is exacerbated by the missing borders that have now been solved in a recent JIRA. Look ahead calculation of null footer values to determine the presence of the hr tag is expensive for a subjective styling decision. I suggest using styling wherever possible to disable the visibility of hr tag. If this not possible in your scenario due to insufficient specificity of IDs etc. in the footer, this issue should be reopened to add the necessary unique identifiers to footer cells.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: