[whatwg] innerHTML for HTML and <plaintext>

Anne van Kesteren annevk at opera.com
Wed Jun 20 05:58:06 PDT 2007

On Mon, 18 Jun 2007 22:26:57 +0200, Ian Hickson <ian at hixie.ch> wrote:
> On Sat, 9 Dec 2006, Anne van Kesteren wrote:
>> On Fri, 08 Dec 2006 22:57:07 +0100, Ian Hickson <ian at hixie.ch> wrote:
>>>> The section "If the child node is a Text or CDATASection node"
>>>> should include the <plaintext> element.
>>> <plaintext> in general isn't supported by the innerHTML spec -- for
>>> example, it would always introduce a new </plaintext> element. Is that
>>> a problem?
>> Yeah, the way the contents of a <plaintext> element node are returned
>> has given Opera at least one interop issue.
> What did you settle on for the implementation? I don't really know how I
> can fix this, given that it is trivial for the <plaintext> element not to
> be the last element in the DOM.

<plaintext> needs to be added to the list of elements the serialization  
algorithm for Text and CDATASection nodes. That is, its contents should  
not be escaped but appended literally. This is basically about  
<plaintext>.innerHTML, not about any other issues <plaintext> introduces.

Anne van Kesteren

More information about the whatwg mailing list