- From: Jacob Rossi <Jacob.Rossi@microsoft.com>
- Date: Wed, 3 Aug 2011 17:19:56 +0000
- To: "www-dom@w3.org" <www-dom@w3.org>, Sergey Ilinsky <sergey@ilinsky.com>
Hi Sergey, In agreement with this thread, we've updated the spec to define that capture phase listeners be invoked on targets. [1] Let us know if you have additional comments/concerns with this change. Thanks, Jacob [1] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#addEventListener_useCapture ================================================= From: Olli Pettay <Olli.Pettay@helsinki.fi> Date: Mon, 27 Sep 2010 15:08:14 +0300 Message-ID: <4CA0892E.2080804@helsinki.fi> To: Stewart Brodie <stewart.brodie@antplc.com> CC: www-dom@w3.org, sergey@ilinsky.com On 09/27/2010 12:42 PM, Stewart Brodie wrote: > Sergey Ilinsky<sergey@ilinsky.com> wrote: > >> As far as I know there are "modern" browsers which handle capture-phase >> event handlers on targets. Is this behaviour wrong or correct? Is the >> correct behaviour specified anywhere in the specification? > > This has been discussed before (although possibly not on this mailing list?) > and I believe that a summary would be: > > * It was completely wrong > * Firefox had this bug [bug 235441, lots of discussion there too] > * Firefox won't fix it because there's a website builder that relies on it Yeah, otherwise correct, except that the reason is more that many web sites relies on the behavior where capturing listeners are called in target phase. -Olli > * Other browsers have started to emulate this fault > * The spec is being retrospectively changed to match Firefox's behaviour > * any content that relied on the original specification is now broken > >
Received on Wednesday, 3 August 2011 17:20:24 UTC