- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Wed, 17 Jun 2009 22:50:50 +0300
- To: Ojan Vafai <ojan@chromium.org>
- CC: Doug Schepers <schepers@w3.org>, Ian Hickson <ian@hixie.ch>, www-dom@w3.org, Daniel Danilatos <danilatos@google.com>
On 6/3/09 12:34 PM, Ojan Vafai wrote: > For example, one idea we came up with for their use case is having > something like a cancellable onExecCommand event that would fire > whenever an execCommand was called and to spec it such that all text > editing is required to go through an execCommand (e.g. undo, redo, > insertText, bold, etc). These are much higher-level and less noisy than > mutation events and wouldn't have a number of problems that mutation > events do (e.g. performance penalties, crashiness complexities, etc). "ExecCommand" event sounds useful, but it should be defined in the same spec where execCommand is defined. Adding "ExecCommand" to DOM Events spec doesn't make much sense, IMO. -Olli
Received on Wednesday, 17 June 2009 19:51:33 UTC