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 (JIRA)" <ji...@apache.org> on 2014/12/05 12:34:13 UTC

[jira] [Resolved] (WICKET-5783) Multiple events in AjaxEventBehavior with prefix 'on'

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

Martin Grigorov resolved WICKET-5783.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 6.19.0
                   7.0.0-M5

I've added javadoc to the class explaining why Wicket cuts the prefix 'on'.
Also I've moved the logic to #getEvent() method. This way is the application needs to use custom event with name like "one" or even "on" then it could override this method.
The method cuts 'on' for all event names.

> Multiple events in AjaxEventBehavior with prefix 'on'
> -----------------------------------------------------
>
>                 Key: WICKET-5783
>                 URL: https://issues.apache.org/jira/browse/WICKET-5783
>             Project: Wicket
>          Issue Type: Bug
>            Reporter: Filipe Roque
>            Assignee: Martin Grigorov
>             Fix For: 7.0.0-M5, 6.19.0
>
>         Attachments: events.zip
>
>
> if multiple events are used and one starts with "on", it only works if it is the first one, because of:
> {code}
> 		if (event.startsWith("on"))
> 		{
> 			event = event.substring(2);
> 		}
> {code}
> Why are events possible to start with "on" ? 
> Is this legacy? Perhaps should be removed for Wicket 7 ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)