You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/01 20:50:21 UTC
[jira] [Commented] (TAP5-2353) It should be possible to unregister
DOM event listeners
[ https://issues.apache.org/jira/browse/TAP5-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117636#comment-14117636 ]
ASF subversion and git services commented on TAP5-2353:
-------------------------------------------------------
Commit 4b0c857b7b08785850b6d399effa53d9aca6a2b0 in tapestry-5's branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=4b0c857 ]
TAP5-2353: It should be possible to unregister DOM event listeners
> It should be possible to unregister DOM event listeners
> -------------------------------------------------------
>
> Key: TAP5-2353
> URL: https://issues.apache.org/jira/browse/TAP5-2353
> Project: Tapestry 5
> Issue Type: Wish
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
> Assignee: Howard M. Lewis Ship
> Fix For: 5.4
>
>
> If a component registers a listener on the document, this listener might prevent JavaScript objects like closures or DOM element being cleaned up.
> ElementWrapper.on should return an Object (EventHandler ?) that can be used to unregister the respective listener.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)