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/04 21:21:12 UTC

[jira] [Comment Edited] (WICKET-5783) multiple events in AjaxEventBehavior

    [ https://issues.apache.org/jira/browse/WICKET-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234576#comment-14234576 ] 

Martin Grigorov edited comment on WICKET-5783 at 12/4/14 8:20 PM:
------------------------------------------------------------------

Wicket 7.x logs a warning that 'on' is not needed. Again only for the first event name, if there are.
Wicket 8.x won't cut the leading 'on' because custom events may have any name.
Wicket 6.x/7.x cuts it because many apps come from pre-6.0 and they usually start with 'on'.

What do you suggest ?


was (Author: mgrigorov):
Wicket 7.x logs a warning that 'on' is not needed. Again only for the first event name, if there are.
What do you suggest ?

> multiple events in AjaxEventBehavior
> ------------------------------------
>
>                 Key: WICKET-5783
>                 URL: https://issues.apache.org/jira/browse/WICKET-5783
>             Project: Wicket
>          Issue Type: Bug
>            Reporter: Filipe Roque
>         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)