W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2012

Re: [whatwg] Submitting contentEditable Content In A Form

From: Ojan Vafai <ojan@chromium.org>
Date: Thu, 13 Sep 2012 14:06:23 -0700
Message-ID: <CANMdWTsJdHNWTMCEtk40uGhf22dvQu5JBqE2X+m_86DABKzdsg@mail.gmail.com>
To: Alain Couthures <alain.couthures@agencexml.com>
Cc: whatwg <whatwg@lists.whatwg.org>, Mikko Rantalainen <mikko.rantalainen@peda.net>
On Fri, Sep 7, 2012 at 1:07 PM, Alain Couthures <
alain.couthures@agencexml.com> wrote:

> Le 07/09/2012 12:32, Mikko Rantalainen a écrit :
>
>  2012-09-07 11:57 Europe/Helsinki: Hugh Guiney:
>>
>>> JavaScript into, say, a hidden form field. I think that there should
>>> be some mechanism to associate contentEditable elements with
>>> forms—maybe the combination of contentEditable="true" and the presence
>>> of @name creates an implicit form control? The value sent to the
>>> server could be equivalent to that element's innerHTML. Thoughts?
>>>
>> The contenteditable attribute is meant for low level wysiwyg-editor like
>> behavior framework and it is not meant to work standalone without
>> scripting.
>>
>> I'd suggest supporting <textarea type="text/html"> with a built-in HTML
>> wysiwyg editor if any UA wants to support HTML editing without
>> JavaScript. In that case, the UA should provide a scriptable method for
>> detecting for native support of type="text/html". As a result, a CMS
>> system could fallback to e.g. TinyMCE or CKeditor to emulate the missing
>> support.
>>
>>  @type should only contain a type name, such as "date" or "number", and
> "text/html" is a media type so "html" would be more appropriate from my
> point of view.
>
> I can mention that XForms has the same problematic and I implemented a
> wysiwyg editor support in my own XForms implementation with TinyMCE for
> XForms textarea control. In XForms, the type associated to the target node
> is used to automatically adapt the control rendering.
>
> BTW, I even consider that "textarea" would be useless if only a
> "multilined" type could be supported for the input field. A select field
> would be an input field for an enumeration... So input tag would cover
> every possibility!
>

I think this is a problem that we need to address more generally. I'm not
sure what the API should look like, but it's not specific to
contentEditable. I should be able to make a Web Component that submits
specific values with forms based off it's content. If we solve that problem
right, it'll be possible to make contentEditable elements submit with forms
without extra JS code.
Received on Thursday, 13 September 2012 21:07:13 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:45 UTC