Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-12441

Library - Controls - Disable on Key Event examples are ambiguous

          Details

          • Type: Bug Fix
          • Status: Closed
          • Priority: 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
          • 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.

              Attachments

                Issue Links

                cloned to

                Bug Fix - A problem which impairs or prevents the functions of the product. KULRICE-12442 Library - Containers - Groups - Section Horizontal not displaying correctly

                • Major - Major loss of function.
                • Closed
                discovered by

                Task - A task that needs to be done. KULRICE-13753 2.4.0 Coordinated Developer Testing (4/9/2014)

                • Major - Major loss of function.
                • Closed

                  Activity

                  Hide
                  Permalink
                  kbtaylor 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
                  kbtaylor 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:
                      kbtaylor Kristina Taylor (Inactive)
                      Reporter:
                      jruch 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