W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [editing] input event should have a data property WAS: [D3E] Where did textInput go?

From: Aryeh Gregor <ayg@aryeh.name>
Date: Thu, 3 May 2012 09:36:19 +0300
Message-ID: <CAKA+AxkKNNDg4dbgw0nLUKkSWYcOBrbeeBaaEdBkrcgzvEzCrA@mail.gmail.com>
To: Ojan Vafai <ojan@chromium.org>
Cc: Andrew Oakley <andrew@ado.is-a-geek.net>, Anne van Kesteren <annevk@opera.com>, WebApps WG <public-webapps@w3.org>
On Thu, May 3, 2012 at 12:44 AM, Ojan Vafai <ojan@chromium.org> wrote:
> As I've said before, I don't think command/value should be restricted to
> contentEditable beforeInput/input events. I don't see any downside to making
> command, value and text all available for all three cases. It simplifies
> things for authors. The code they use for plaintext inputs can be the same
> as for rich-text inputs.

If command/value make any sense for plaintext inputs, yes.  As
specced, and AFAICT as implemented in Gecko and Opera, execCommand()
only operates on the contents of contenteditable areas, not plaintext
inputs.  If that were changed to match (AFAICT) IE and WebKit, then
I'd agree that it would make sense to expose the same properties.
Received on Thursday, 3 May 2012 06:37:10 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:40 UTC