W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2010

Re: [DOM Level 3 Events] optionality of the capture argument in addEventListener/removeEventListener

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Sun, 03 Oct 2010 14:14:37 +0300
Message-ID: <4CA8659D.7050601@helsinki.fi>
To: Ojan Vafai <ojan@chromium.org>
CC: Jonas Sicking <jonas@sicking.cc>, Sergey Ilinsky <sergey@ilinsky.com>, www-dom@w3.org
On 10/01/2010 08:20 PM, Ojan Vafai wrote:
> On Wed, Sep 29, 2010 at 8:31 PM, Jonas Sicking <jonas@sicking.cc> wrote:
>
>     On Wed, Sep 29, 2010 at 10:04 AM, Olli Pettay
>     <Olli.Pettay@helsinki.fi <mailto:Olli.Pettay@helsinki.fi>> wrote:
>      > I don't support this kind of change.
>      > It happens way too often that people don't think about the phase,
>     and that
>      > leads to bugs.
>
>     I don't think requiring the last argument is helping a whole lot with
>     that right now. I've heard multiple times developers say:
>
>     "I don't know why I have to specify the last 'false' value, but I have
>     to do that everywhere when I call addEventListener".
>
>
> In addition to this, I've seen many developers toggle the boolean value
> because it happened to fix a specific bug without understanding why (and
> it usually caused other bugs). Forcing people to use the boolean is not
> synonymous with forcing them to understand it.
>
> Ojan

But effectively removing the parameter means that even
fewer web developers understand DOM propagation model in the future,
I believe.


-Olli
Received on Sunday, 3 October 2010 11:15:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:06 GMT