You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/02 11:49:23 UTC

[jira] [Resolved] (WICKET-4482) Regression in OnChangeAjaxBehavior

     [ https://issues.apache.org/jira/browse/WICKET-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4482.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 6.0.0-RC1

Appoach 1) was applied. It works fine and preserves the behavior from 1.5.x
                
> Regression in OnChangeAjaxBehavior
> ----------------------------------
>
>                 Key: WICKET-4482
>                 URL: https://issues.apache.org/jira/browse/WICKET-4482
>             Project: Wicket
>          Issue Type: Task
>          Components: wicket
>    Affects Versions: 6.0.0-beta1
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 6.0.0-RC1
>
>         Attachments: WICKET-4482.patch
>
>
> There is a regression in 6.x in OnChangeAjaxBehavior.
> This is a behavior that handles 'oninput' JavaScript event in browser portable way for text form components. In 6.x it is reimplemented with custom jQuery event 'inputchanged'.
> Now I noticed that in 1.5.x and earlier it actually behaves like simple AjaxFormComponentUpdatingBehavior("onchange") for non-text form components.
> I see two solutions:
> 1) change the event to "change.inputchanged". Need to verify it but I think it will be fired when used with DropDownChoice
> 2) rename it to OnInputAjaxBehavior and update its javadoc that it applies only to text components. It can even throw exceptions if used with something else. Just as AjaxFormChoiceComponentBehavior does. And explain that AjaxFormComponentUpdatingBehavior("onchange") should be used for non-text form components.
> I'm more in favour of 2).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira