On Fri, Jun 20, 2014 at 8:28 PM, Ryosuke Niwa <[email protected]> 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.
