[
https://issues.apache.org/jira/browse/WICKET-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-288.
----------------------------------
Resolution: Fixed
Assignee: Igor Vaynberg (was: Matej Knopp)
> Better separate new event handling from ajax
> --------------------------------------------
>
> Key: WICKET-288
> URL: https://issues.apache.org/jira/browse/WICKET-288
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3, 2.0
> Reporter: Igor Vaynberg
> Assigned To: Igor Vaynberg
> Fix For: 1.3, 2.0
>
> Attachments: patch.txt
>
>
> right now you need to have something ajaxy on the page to take benefit of new
> event loading. what the attached patch does is break out event stuff into
> wicket-event.js that is included automatically by headerresponse if one of
> those funcs is called. it is also automatically included by the ajax behavior.
> i havent tested the patch, so take a look and give me feedback - its just an
> idea because i noticed eelco manually including wicket-ajax.js into
> datepicker since it needs onload event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
