Re: textInput --> beforeInput [ISSUE-121] from Tony Chang on 2010-09-10 (www-dom@w3.org from July to September 2010)

From: Tony Chang <tony@chromium.org>
Date: Fri, 10 Sep 2010 10:39:45 -0700
To: Anne van Kesteren <annevk@opera.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Doug Schepers <schepers@w3.org>, Ojan Vafai <ojan@chromium.org>, www-dom@w3.org
Message-ID: <AANLkTik2YH2UOO72uVnY7vmMcmwmp49vB+7EPcbKpGOM@mail.gmail.com>

On Fri, Sep 10, 2010 at 10:38 AM, Anne van Kesteren <annevk@opera.com>wrote:

> On Fri, 10 Sep 2010 19:33:26 +0200, Jonas Sicking <jonas@sicking.cc>
> wrote:
>
>> What is the advantage of the rename though? I personally think
>> textInput is more intuitive, but I don't feel strongly.
>>
>
> It works better together with the 'input' event we already have.

'text' is also confusing because in a content editable region,
cut/paste/undo/redo can insert or remove things other than text (e.g., an
image).

Received on Friday, 10 September 2010 17:40:15 UTC