On Fri, May 30, 2014 at 12:50 AM, Julie Parent <jpar...@gmail.com> wrote:
> 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?

Just a DOM API perhaps as you're not going to get far without
scripting anyway? Interaction with contentEditable features will have
to be defined. This could maybe throw if the element was already
editable and if this is already active, maybe contentEditable stuff
should have no effect.


Reply via email to