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

RE: [editing] Changing Default Intentions

From: Ben Peters <Ben.Peters@microsoft.com>
Date: Mon, 23 Jun 2014 22:56:31 +0000
To: Ryosuke Niwa <rniwa@apple.com>
CC: "public-webapps@w3.org" <public-webapps@w3.org>, "public-editing-tf@w3.org" <public-editing-tf@w3.org>
Message-ID: <36c6cadc65a64ed898bdeca1957f3451@BLUPR03MB437.namprd03.prod.outlook.com>
On Fri, Jun 20, 2014 at 8:28 PM, Ryosuke Niwa <rniwa@apple.com> wrote:
> This means execCommand is available for other uses. Since it's a legacy API that doesn't have the best shape, perhaps it is best to tie it to the legacy behavior. So the image [1] now shows that execCommand (lower right) would cause the browser to actually perform the command, not fire a CommandEvent. In effect, execCommand('bold') is the default behavior for CommandEvent type bold in contentEditable="true". In contentEditable="minimal" or equivalent, CommandEvent type bold has no default. If a site wishes to use the built-in bold, they can call execCommand('bold') in the CommandEvent, thereby restoring contentEditable="true" behavior for that specific command.
> execCommand not triggering command event seems like a promising approach.  I think we really need a concrete list of use cases here though.  It's hard to design & evaluate proposals without having a list of concrete use cases against which we're evaluating proposals.

Agreed. Better use cases and goals is my next project. Expect an update soon.
Received on Monday, 23 June 2014 22:57:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:25 UTC