This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14762 - Rename all callbackInterface.handleEvent methods to something which describes what the method is about
Summary: Rename all callbackInterface.handleEvent methods to something which describes...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-10 11:54 UTC by Olli Pettay
Modified: 2011-12-07 22:59 UTC (History)
4 users (show)

See Also:

Attachments

Description Olli Pettay 2011-11-10 11:54:09 UTC 

    


    


      



        
          Comment 1
        

        
          Ian 'Hixie' Hickson

        

        
        

        
          2011-11-10 23:51:50 UTC
        

      






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.

    


    


      



        
          Comment 2
        

        
          Ian 'Hixie' Hickson

        

        
        

        
          2011-11-10 23:52:01 UTC
        

      






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

    


    


      



        
          Comment 3
        

        
          Olli Pettay

        

        
        

        
          2011-11-10 23:55:20 UTC
        

      






This was also discussed during TPAC and afaik people in general where favoring
sane method names.

    


    


      



        
          Comment 4
        

        
          Ian 'Hixie' Hickson

        

        
        

        
          2011-11-11 22:26:24 UTC
        

      






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.

    


    


      



        
          Comment 5
        

        
          Ian 'Hixie' Hickson

        

        
        

        
          2011-12-07 22:59:32 UTC
        

      






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