[
https://issues.apache.org/jira/browse/WICKET-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194583#comment-14194583
]
Nick Pratt commented on WICKET-5746:
------------------------------------
(With ref to https://issues.apache.org/jira/browse/WICKET-5747) Wont this be a
little confusing for developers who read the JS/HTML with the expectation that
the defined events will fire in the order defined. Having an additional event
to fire once everything is ready seems like a duplication of functionality of
OnDomReady. What in Wicket necessitates the requeueing? If this JS event
requeueing is required, then shouldn't all of the Wicket onDomReadyHeaderItems
be added to this new event method invocation, and not added to the current
<script> element - the expectation of devs (at least the 3 I just discussed
this with) is that the events fire in the order defined, and that it's
confusing when they do not.
> Fire an event once all JS event listeners are registered
> --------------------------------------------------------
>
> Key: WICKET-5746
> URL: https://issues.apache.org/jira/browse/WICKET-5746
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.18.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 7.0.0-M5, 6.19.0
>
>
> Fire a global event once all Wicket.Ajax.ajax() calls have been executed.
> See http://markmail.org/message/i662uiv6eiiqh72x
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
