[whatwg] What exactly is contentEditable for?

[Matthew Raymond]

Jim Ley wrote:
> On 8/30/05, Matthew Raymond <mattraymond at earthlink.net> wrote:
>>  Oh, I think I get it. You don't necessarily want there to be toolbars
>>and the like,
> 
> No, I want contentEditable left as is, because not all the use cases
> and delivered products of contentEditable are applicable to full
> spectrum HTML authoring, they're limited to elements, no CSS, they're
> limited in what elements they use etc.   A UA toolbar in a textarea
> accept="text/html" would be a great idea.

   I'd really prefer not to limit user agents in any way. (People will
just create plug-ins for the desired functionality anyway.) If IE has
the ideal UI, then market forces will naturally lead other UA vendors to
follow suit(sp?).

>>Is a simple, straight-forward rich editing
>>control too much to ask for?
> 
> Absolutely not, but it's not the same thing as contentEditable, it has
> different use cases, that's all I'm saying, we need both, not just
> one.

   I'm actually proposing we have |contenteditable|, <textarea accept>
AND <htmlarea>, so I don't need any convincing. I just don't think it's
wise to make UI decisions for the UA vendors, that's all.