Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-2424

OnChangeAjaxBehavior + DatePicker do not work together

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.4.8, 1.5-M1
    • Component/s: wicket, wicket-extensions
    • Labels:
      None
    • Environment:
      Firefox, IE

      Description

      DatePicker fails to notify component update when OnChangeAjaxBehavior is used on the target input.
      It works well with AjaxFormComponentUpdatingBehavior.

      The root cause seems to be in the Wicket.ChangeHandler added by the OnChangeAjaxBehavior, which hides user handler while the DatePicker calls onchange handler directly (wicket-date.js:186):
      if (field.onchange != null && typeof(field.onchange) != 'undefined') field.onchange();

      Possible fix could be dispatching onchange Event instead of direct handler invocation.
      Yet I don't know what is purpose of Wicket.ChangeHandler here...

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ivaynberg Igor Vaynberg
                Reporter:
                varlax Alexey Varlamov
              • Votes:
                1 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: