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

evaluateOnKeyUp does not capture events when browser autocomplete values are selected

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.4
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      When:
      An input control has evaluateOnKeyUp, and
      A user selects a value from their browser's autocomplete/autosuggest list,

      No events are captured, therefor the evaluation is never run.

      To circumvent this, temporarily, we added the following code:

      function toggleTextBoxes(textBox){
      jQuery(textBox).bind('input', function(event)

      { jQuery(textBox).keyup(); console.log(event); }

      );
      }

      Which is called by the onclick event.

      This allows us to capture any events, and simulate the keyup event to trigger the evaluation.

        Attachments

          Issue Links

            Activity

            Hide
            bsmith Brian Smith (Inactive) added a comment -

            Did some re-investigation on this, the solution above won't work for us because it will generate two keyup per a keystroke. We need to change our keyups to use the input event wholesale but this has design implications for component and things which currently use keyup. Also the input event is not supported in IE8 (and has a small bug in IE9) which would require a workaround. See for explanation of all this stuff: http://benalpert.com/2013/06/18/a-near-perfect-oninput-shim-for-ie-8-and-9.html including explanation of why we need to support the onInput event for KRAD.

            Show
            bsmith Brian Smith (Inactive) added a comment - Did some re-investigation on this, the solution above won't work for us because it will generate two keyup per a keystroke. We need to change our keyups to use the input event wholesale but this has design implications for component and things which currently use keyup. Also the input event is not supported in IE8 (and has a small bug in IE9) which would require a workaround. See for explanation of all this stuff: http://benalpert.com/2013/06/18/a-near-perfect-oninput-shim-for-ie-8-and-9.html including explanation of why we need to support the onInput event for KRAD.

              People

              • Assignee:
                bsmith Brian Smith (Inactive)
                Reporter:
                davpoind David Poindexter (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: