Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-12441

Library - Controls - Disable on Key Event examples are ambiguous

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
      Trunk
    • Similar issues:
      KULRICE-10771KRAD Demo Library Controls demonstrating Disable on keyup events initially disabled
      KULRICE-13804Fill AFT Per-screen item gap: KRAD Library: Controls: Radio (new item)
      KULRICE-13709Fill AFT Per-screen item gap: KRAD Library: Controls: Checkbox (new items)
      KULRICE-13790Fill AFT Gap: Kitchen Sink: Event Examples
      KULRICE-11309Library Control Password Disable when changed doesn't disable
      KULRICE-8126Collection control does not honor disable if disable is disabled by an expression for collection refresh
      KULRICE-11897Library - Client Responsiveness - Disable - onKeyUp/onChange broken
      KULRICE-13117Disable Date Picker Control when the field is disabled
      KULRICE-9991Component Library: KIM User example not working
      KULRICE-10595Library widgets suggest examples not working
    • Rice Module:
      KRAD
    • Application Requirement:
      Rice
    • Sprint:
      2.4.0-rc1 Sprint 8
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Library - Controls - Disable on Key Event examples are ambiguous.

      Many of the controls have a 'Disable on Key Event' example. The title should be enable on key event as the example starts off as disabled and then becomes enable on a key event. The controls with this include Radio Control, Text Control, Text Area Control, Password Control.

        Issue Links

          Activity

          Hide
          Kristina Taylor (Inactive) added a comment -

          Actually, the problem here is that the examples (including Checkbox which uses it slightly differently) are demonstrating the evaluateDisabledOnKeyUp property, so the name should probably be "Evaluate Disabled on Key Up". That way it keeps the consistency of demonstrating properties. I think adding "Evaluate" should help since it notes that it is evaluating whether it should be disabled on every key up. I will also make Checkbox work consistently with this.

          Show
          Kristina Taylor (Inactive) added a comment - Actually, the problem here is that the examples (including Checkbox which uses it slightly differently) are demonstrating the evaluateDisabledOnKeyUp property, so the name should probably be "Evaluate Disabled on Key Up". That way it keeps the consistency of demonstrating properties. I think adding "Evaluate" should help since it notes that it is evaluating whether it should be disabled on every key up. I will also make Checkbox work consistently with this.

            People

            • Assignee:
              Kristina Taylor (Inactive)
              Reporter:
              Jeff Ruch
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 hour
                1h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour
                1h

                  Agile

                    Structure Helper Panel