Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: CSS, User Experience (UX)
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Epic Link:
    • Rice Module:
      KRAD
    • Application Requirement:
      KC
    • Sprint:
      2.4.0-m2 Sprint 2, 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

      The current design of the application menu is hard to replicate in the theme. There are inline styles and requirements on HTML 5. Also, the design for the menus requires a fixed width, and the does not adjust based on contents.

        Attachments

          Issue Links

            Activity

            Hide
            thrclark Tom Clark added a comment -

            The 2 day time estimate could change in either direction. Bootstrap 3 is introducing some occasional HTML5 dependancies & semantics, which aren't always supported in KRAD.

            We can get by with css overrides (quick fix - less than 2 days), or refactor KRAD's html to be more compliant with HTML5 standards & semantics (lasting fix - much more than 2 days, requiring broader discussions).

            Show
            thrclark Tom Clark added a comment - The 2 day time estimate could change in either direction. Bootstrap 3 is introducing some occasional HTML5 dependancies & semantics, which aren't always supported in KRAD. We can get by with css overrides (quick fix - less than 2 days), or refactor KRAD's html to be more compliant with HTML5 standards & semantics (lasting fix - much more than 2 days, requiring broader discussions).
            Hide
            thrclark Tom Clark added a comment -

            http://ux.kuali.org/prototypes/kc/p2-prototype-b1/index.php

            The inline styles in the menu have been moved to external LESS files, and the width of the drop down areas can be varied according to content requirements. The prototypes rely on Bootstrap's DOM and usage of html5 elements.

            The required LESS files have been checked into both 2.4 trunk and the prototypes svn.

            I would recommend that we consider DOM cleanup in the current KRAD applicationHeader to take advantage of Bootstrap's lighter DOM structure and use of html5 elements.

            Show
            thrclark Tom Clark added a comment - http://ux.kuali.org/prototypes/kc/p2-prototype-b1/index.php The inline styles in the menu have been moved to external LESS files, and the width of the drop down areas can be varied according to content requirements. The prototypes rely on Bootstrap's DOM and usage of html5 elements. The required LESS files have been checked into both 2.4 trunk and the prototypes svn. I would recommend that we consider DOM cleanup in the current KRAD applicationHeader to take advantage of Bootstrap's lighter DOM structure and use of html5 elements.
            Hide
            jkneal Jerry Neal (Inactive) added a comment -

            Tom,

            We will drop the current header and replace it with what you have here. Does the prototype reflect the DOM structure you would like to see?

            Jerry

            Show
            jkneal Jerry Neal (Inactive) added a comment - Tom, We will drop the current header and replace it with what you have here. Does the prototype reflect the DOM structure you would like to see? Jerry
            Hide
            thrclark Tom Clark added a comment -

            The prototype appHeader DOM feels pretty solid to me - it's inline with 'bootstrap best practices' I think we can go with it. There's some minor responsive design issues to address, but that can be handled outside of the DOM via css/less.

            Show
            thrclark Tom Clark added a comment - The prototype appHeader DOM feels pretty solid to me - it's inline with 'bootstrap best practices' I think we can go with it. There's some minor responsive design issues to address, but that can be handled outside of the DOM via css/less.

              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 - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 2 days
                  2d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified