Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

On May 29, 2014, at 3:50 PM, Julie Parent <> wrote:

> Without default text input, the current proposal for contentEditable="minimal" is essentially just enabling cursors (drawing them, dispatching events, performing default actions).  Rather than calling the mode "minimal", which is ill-defined, why not explicitly call it what it is: "cursor-only"?  Or, have contentEditable take a list of features to turn enable: contentEditable="enable-cursors enable-CommandEvents".
> Or, rather than tying this concept to contentEditable, with all the assumptions and complications that brings up, why not expose this building block as a completely separate attribute?

Explicitly listing features to enable sounds like a superior approach.

- R. Niwa

Received on Friday, 6 June 2014 16:55:48 UTC