Added option to override change event

[abe1001]

Sometimes we need onChange on other events than 'change'. For example 'keyup'. This is useful when you want to validate while the user is typing the text. In this proposal you only have to add a "overrideInputEvent": "keyup" attribute to the field you want to give other input event than change.

[jdorn]

I like the idea. A couple things:

• In general, I prefer using schema options for non-standard parameters instead of adding new schema keywords. So, something like this instead:

{
  "type": "string",
  "options": {
    "input_event": "keyup"
  }
}

• Listening only on keyup has some problems. For example, right click paste and browser auto-complete does not fire keyup. Listening to both change and keyup fixes these issues. Maybe the code should always listen on change and there's a boolean option for also enabling keyup.

[abe1001]

I agree. I will create a new suggestion.

[jericmason]

Any update on the status for this request? The one problem I can see with the solution in the pull-request is that it only allows a single additional event to be included. This could be used to capture real-time key editing or real time copy-paste via mouse click, but it couldn't handle both possible ways the content may change in real time. I suggest that if this is to be included as a json schema field it should take the form of an array rather than single parameter.

{
  "type": "string",
  "options": {
    "input_events": [ "keyup", "click" ]
  }
}

[ghost]

Any update regarding adding option to override change event