[
https://issues.apache.org/jira/browse/WICKET-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100659#comment-16100659
]
ASF GitHub Bot commented on WICKET-6427:
----------------------------------------
Github user martin-g commented on a diff in the pull request:
https://github.com/apache/wicket/pull/223#discussion_r129408806
--- Diff:
wicket-core/src/main/java/org/apache/wicket/markup/head/ResourceAggregator.java
---
@@ -353,6 +353,7 @@ private void renderCombinedEventScripts()
}
if (combinedScript.length() > 0)
{
+
combinedScript.append("\nWicket.Event.publish(Wicket.Event.Topic.AJAX_TIMERS_BOUND);");
--- End diff --
Yes, I think we should publish both for 8.x and remove
`AJAX_HANDLERS_BOUND` for 9.x.
We can also log a warning when `AJAX_HANDLERS_BOUND` published to a
subscriber.
> Fire an event once all ajax timers are registered
> -------------------------------------------------
>
> Key: WICKET-6427
> URL: https://issues.apache.org/jira/browse/WICKET-6427
> Project: Wicket
> Issue Type: Improvement
> Reporter: Jezza
> Priority: Minor
>
> This is in the same vein as WICKET-5746.
> I just need some way to execute code after the timers have been registered,
> and it seemed weird to only have the event fired for one set of ajax related
> calls.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
