14762 2011-11-10 11:54:09 +0000 Rename all callbackInterface.handleEvent methods to something which describes what the method is about 2011-12-07 22:59:32 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Linux RESOLVED WONTFIX P2 normal --- 1 bugs ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 59831 0 bugs 2011-11-10 11:54:09 +0000 59860 1 ian 2011-11-10 23:51:50 +0000 Consistently calling callbacks handleEvent() makes it easier for authors to know what to call their callbacks, so I think it's better to be consistent here. 59861 2 ian 2011-11-10 23:52:01 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: see comment 1 59862 3 bugs 2011-11-10 23:55:20 +0000 This was also discussed during TPAC and afaik people in general where favoring sane method names. 59976 4 ian 2011-11-11 22:26:24 +0000 handleEvent() seems quite sane to me, at least insofar as using an object with a method instead of a closure is sane at all, which is another matter. Using different names here would mean that one could not simply use the same callback mechanism for all callbacks, which seems like a loss. It's not clear what benefit there is in using different names; the only place one would see these names is in the very place that passes the callback, where it's pretty unambiguous what's going on anyway. 61146 5 ian 2011-12-07 22:59:32 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: see comment 4