W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

before/after editaction

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Tue, 30 Aug 2011 16:00:06 -0700
Message-ID: <CABNRm61thki9fG2a_BsVOVdwHHXNGD_YPM867uQGnMNbmp69+Q@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>
Cc: Alex Russell <slightlyoff@chromium.org>, Ojan Vafai <ojan@chromium.org>, Jonas Sicking <jonas@sicking.cc>, Ehsan Akhgari <ehsan@mozilla.com>, Annie Sullivan <sullivan@chromium.org>, Aryeh Gregor <Simetrical+w3c@gmail.com>, Anne van Kesteren <annevk@opera.com>
Greetings all,

During the very constructive meeting in
Toronto<http://ehsanakhgari.org/blog/2011-08-31/future-editing-web>,
we came to a conclusion that we want events that fire before after user
editing action and execCommand take place.  Let us call these events
beforeEditAction and afterEditAction respectively.

>From Ehsan's blog:

> The beforeeditaction event would fire before the browser initiates handling
> of an editing command.  It would be cancelable, so that web applications
> which do not want certain commands enabled can just cancel the respective
> events.  The aftereditaction event would fire when the browser is done
> performing the editing action.  This event will provide semantic information
> about the editing operation performed, and will allow web content to alter
> the DOM generated as a result of the editing action.  Think of a web
> application which wants to use strong tags instead of b tags for bold text
> generated by the bold command.  With aftereditaction, the web application
> can just fix up the DOM after the browser has modified it to
> use strong tags.


Can we add these events?

Best regards,
Ryosuke Niwa
Software Engineer
Google Inc.
Received on Tuesday, 30 August 2011 23:06:21 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT