- From: <bugzilla@jessica.w3.org>
- Date: Sat, 06 Aug 2011 06:08:38 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13686 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |WONTFIX --- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-06 06:08:37 UTC --- I don't think changing addEventListener() makes sense. It's one thing to have an attribute with magic, it's quite another to have an API that is magical only in certain circumstances. Anyway, it doesn't make sense to make addEventListener() magical here. If you're using it, you almost certainly are doing something more complicated than just hooking a listener and using the port — you're probably hooking a series of listeners, possibly not all in the same task, each to look for one particular type of message. IIRC there's an example of this in the spec. For that use case, it doesn't make sense to start the port quickly. -- 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 Saturday, 6 August 2011 06:08:40 UTC