Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: CSS
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Epic Link:
    • Rice Module:
      KRAD
    • Sprint:
      2.4.0-m2 KRAD Sprint 3
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      kboot.less is including files that are also included by bootstrap.less. This causes duplicate CSS classes in the resulting CSS. We don't need to include these files in kboot

        Attachments

          Activity

          Hide
          thrclark Tom Clark added a comment -

          A problem that I'm encountering here...'mix-ins' have been used to bridge the gap between uif and bootstrap styling. Without the original bootstrap files in the kboot theme directory (the 'duplicate files' in question), mix-ins won't work properly, and the LESS files will not compile.

          As long as we're using uif class names to render a visual styling base offered by Bootstrap, mix-ins (and thus, the duplicate files) are required.

          In order to move away from mix-in usage, we need to convert some uif classes in the DOM to use bootstrap classes (e.g. 'uif-primaryActionButton' changes to 'btn btn-primary', etc...) Once we fully move away from mix-ins, we can delete the duplicate files.

          Sub-tasks forthcoming...

          Show
          thrclark Tom Clark added a comment - A problem that I'm encountering here...'mix-ins' have been used to bridge the gap between uif and bootstrap styling. Without the original bootstrap files in the kboot theme directory (the 'duplicate files' in question), mix-ins won't work properly, and the LESS files will not compile. As long as we're using uif class names to render a visual styling base offered by Bootstrap, mix-ins (and thus, the duplicate files) are required. In order to move away from mix-in usage, we need to convert some uif classes in the DOM to use bootstrap classes (e.g. 'uif-primaryActionButton' changes to 'btn btn-primary', etc...) Once we fully move away from mix-ins, we can delete the duplicate files. Sub-tasks forthcoming...
          Hide
          thrclark Tom Clark added a comment -

          Resolution of this jira is contingent on completion of sub-tasks

          Show
          thrclark Tom Clark added a comment - Resolution of this jira is contingent on completion of sub-tasks

            People

            • Assignee:
              thrclark Tom Clark
              Reporter:
              jkneal Jerry Neal (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours
                4h
                Remaining:
                Remaining Estimate - 4 hours
                4h
                Logged:
                Time Spent - Not Specified
                Not Specified