- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Wed, 22 Jun 2011 23:51:34 +0300
- To: Rob Brackett <rbrackett@apple.com>
- CC: www-dom@w3.org, Cameron McCormack <cam@mcc.id.au>, Jacob Rossi <jrossi@microsoft.com>
On 06/22/2011 11:44 PM, Rob Brackett wrote: > I wanted to follow up on this, since there haven't been any responses > this week. Does anybody have any feedback on whether the issue of how > ECMAScript functions that also have a handleEvent property behave as > event listeners is an issue worth addressing? I definitely think it > is a legitimate point of confusion for authors and deserves some > discussion, especially since DOM Level 3 Events is closing down. D3E could be clarified, but seems like this is anyway defined in WebIDL. Jacob, could you perhaps add some clarification to D3E? -Olli > > -Rob > > > On Jun 17, 2011, at 9:56 PM, Rob Brackett wrote: > >> On Jun 17, 2011, at 9:26 PM, Boris Zbarsky<bzbarsky@MIT.EDU> >> wrote: >> >>> On 6/17/11 11:07 PM, Rob Brackett wrote: >>>> But it seems disappointing that such flexibility and >>>> consistency in the API would be sacrificed for an optimization >>>> in Internet Explorer. >>> >>> Not just IE. The behavior currently in the spec is the behavior >>> that Chrome, Gecko, and IE have, no? >> >> I was referring to the fact that, in the earlier email, it sounded >> like the *optimization,* and thus the desire for the current >> behavior, was unique to IE. >> >> But to answer the question: yes; IE, Gecko, and Chrome match the >> current spec. However, any WebKit implementation that uses >> JavaScriptCore, which I believe represents a wide variety of mobile >> browsers using WebKit (not just iOS), currently differs from the >> spec. So not all implementations agree. >> >> -Rob >> > > >
Received on Wednesday, 22 June 2011 20:52:49 UTC