- From: <bugzilla@jessica.w3.org>
- Date: Sat, 06 Aug 2011 09:42:40 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13686 Olli Pettay <Olli.Pettay@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |bzbarsky@mit.edu Resolution|WONTFIX | --- Comment #5 from Olli Pettay <Olli.Pettay@gmail.com> 2011-08-06 09:42:39 UTC --- (In reply to comment #3) > Anyway, it doesn't make sense to make addEventListener() magical here. Why does it make sense to have onmessage magical then. onmessage is the only magical onfoo listener there is, and we shouldn't design inconsistent APIs. Atm there are two inconsistencies. onmessage vs addEventListener and onmessage vs other onfoo listeners. What I'd really like to see is to removal of both inconsistencies, but making just the MessagePort API internally somewhat consistent by having onmessage and addEventListener working the same way could be enough. -- 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 09:42:41 UTC