Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-13957Tooltips on input fields with left label cause the input to slip under the label
      KULRICE-10606KRAD Kitchen Sink Input Field labels are not rendering on the left correctly
      KULRICE-12378Rice sampleapp KRAD Kitchen Sink Input Fields Text Controls Right and Left labels are on top
      KULRICE-12086Create Automated Functional (Smoke) Test for KRAD Labs - Kitchen Sink: Input Fields (1)
      KULRICE-13404Fill AFT Gap: Kitchen Sink: Input Fields (part 2)
      KULRICE-11750Remove field label position option
      KULRICE-8980'Add all' option for lookup criteria field does not work with rich options
      KULRICE-7694input field assumes option value of type string
      KULRICE-5138Add pop up text area option for TextAreas and Text input fields
      KULRICE-10646Add input field samples with withWidgetOnly options in krad libary
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      The decision to remove the left label for input fields made certain view harder to create. When you have an isolated input field, it is very inconvenient to throw it in a css grip just to get the label to the left.

      We want to add back the label left option for input fields.

        Activity

        Hide
        Jerry Neal (Inactive) added a comment -

        Brian,

        I am not sure if we are having a 2.4.3 or not, so this might need to go into 2.5 (trunk). Please hold off on commits until I find out.

        Jerry

        Show
        Jerry Neal (Inactive) added a comment - Brian, I am not sure if we are having a 2.4.3 or not, so this might need to go into 2.5 (trunk). Please hold off on commits until I find out. Jerry
        Hide
        Kristina Taylor (Inactive) added a comment -

        We will most likely not have a 2.4.3 release, so put it on trunk.

        Show
        Kristina Taylor (Inactive) added a comment - We will most likely not have a 2.4.3 release, so put it on trunk.

          People

          • Assignee:
            Brian Smith (Inactive)
            Reporter:
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 4 hours Original Estimate - 4 hours
              4h
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day
              1d

                Structure Helper Panel