On Mon, Jun 16, 2014 at 5:48 PM, Julie Parent <jpar...@google.com> wrote: > > Yes. I really like the idea of explicitly enabling what you want and of > separating the concepts. Being able to turn on commandEvents independent of > a cursor seems useful. An API like this leaves far fewer questions of "what > does it do?" than contentEditable="minimal". What does cursor="true" do? It > turns on the ability for the user or developer to place a cursor, and > default movement. It has nothing to do with dom modification. What does > commandEvents="true" do? It enables dispatching commandEvents. No > ambiguity. However, this does make me think again about using > beforeinput/input events rather than adding new CommandEvents, since those > would include drag/drop and clipboard as well?
The way I see it is that <div>not editable at all</div> would get clipboard and drag/drop events, like it does today. <div commandEvents="true">build an editor here</div> would also get CommandEvents.
