- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Oct 2011 00:42:50 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13686 Jacob Rossi [MSFT] <jrossi@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #22 from Jacob Rossi [MSFT] <jrossi@microsoft.com> 2011-10-27 00:42:49 UTC --- (In reply to comment #21) > What the spec currently says is the least bad compromise, IMHO. I think what is in the spec is worse. While I too hate boilerplate code, but I'd rather have to call start() always (whether addEventListener or event handler attribute) than have it behave one way for one registration method and another for the other method. Here's another idea: Let's remove the start() API altogether. Once a message port is constructed, it's started. It's up to the application to ensure it is ready to handle messages before giving the port out. Is there really a valuable scenario where you need to create a port and add listeners but not have started it yet? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 27 October 2011 00:42:53 UTC