Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-5816

invalid use of bootstrap classes for table column widths

XMLWordPrintable

    • ODC Sprint 202, ODC Sprint 203
    • Low

      Description of problem:

      Bootstrap table classes were used to give table columns different widths. It looks like these classes are no longer supported as several tables which use these classes are displayed with even width columns even when different bootstrap column width classes are assigned

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Go to the knative revisions list page

      Actual results:

      observe all columns are evenly spaced

      Expected results:

      conditions columns should be 1/2 the width of the others
      The following is the table column classes for the revisions table:

      export const tableColumnClasses = [
       'col-lg-2 col-md-2 col-sm-4 col-xs-6',
       'col-lg-2 col-md-2 col-sm-4 col-xs-6',
       'col-lg-2 col-md-2 col-sm-4 hidden-xs',
       'col-lg-2 col-md-2 hidden-sm hidden-xs',
       'col-lg-1 col-md-2 hidden-sm hidden-xs',
       'col-lg-1 col-md-2 hidden-sm hidden-xs',
       'col-lg-2 col-md-2 hidden-sm hidden-xs',
       Kebab.columnClass,];
      

      Reproducibility (Always/Intermittent/Only Once):

      always

      Build Details:

      Additional info:

      • There are still several instances of `tableColumnClasses` width assigned bootstrap grid classes such as `col-lg-1` whereas the new PF supported classes are `pf-m-width-20`.
        • knative revisions
        • knative route
        • helm release history
        • helm release resources
        • helm revisions
        • helm release list
        • pipeline table
        • ...

              abhindas Abhinandan Das
              christianvogt Christian Vogt
              Gajanan More Gajanan More (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: