[
https://issues.apache.org/jira/browse/TAP5-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841458#comment-13841458
]
Howard M. Lewis Ship commented on TAP5-2252:
--------------------------------------------
My biggest mistake in the past was to come up with these hypothetical scenarios
and try to brew up a solution in advance ... then the real use case presents
itself, and the hypothetical solution is actually a hinderance, not a help.
As documented, the callback is typically expected to change the element so that
it does not match subsequent scans.
I have thought about having dom.scanner() return a function to de-register the
scanner ... but I can't think of where that would be specifically useful.
> dom.scanner should support a cleanup callback
> ---------------------------------------------
>
> Key: TAP5-2252
> URL: https://issues.apache.org/jira/browse/TAP5-2252
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
>
> In addition to a selector and a create callback, dom.scanner should support a
> (probably optional) cleanup callback that is executed at
> events.zone.willUpdate.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
