63164 - editorshell.CreateElementsWithDefaults() should be able to create non html elements.

Status: VERIFIED WONTFIX

(Core :: DOM: Editor, defect)

Description

[David McNamara]

As the editor can now handle non-html elements it follows that 
editorshell.CreateElementsWithDefaults() should be able to create non html 
elements.

To reproduce: call editorshell.CreateElementsWithDefaults("duck")
What happens: It currently throws a component error.
Build: Mozilla 0.6

Comment 1

[kinmoz]

The error probably occurs because CreateElementWithDefaults() calls
CreateHTMLContent() internally.

Reassigning to [e-mail] ... I think he may have been the original
author of this method.

In the meantime I believe you can accomplish what you want to do by using
document.createElement("duck") and then using editorShell.InsertElement() to
insert it into the document.

Comment 2

[David McNamara]

i just tried document.createElement("duck") and that doesn't work either.
i suspect editorshell.CreateElementsWithDefaults() actually calls 
document.createElement() on a lower level.

Comment 3

[Charles Manske]

The editor can handle non-html elements? I don't think so -- the "rules" system
assumes only HTML. We operate according to the HTML 4 DTD.

Comment 4

[rubydoo123]

marking wontfix, the current editor model is to not allow the user to create 
non-html 4.0 elements.

Comment 5

[David McNamara]

The editor _can_ handle non-html elements and render them with css. It seems a 
shame that it cannot create non-html elements. I was hoping to create a xpfe 
xml-editor in this way.

Comment 6

[sujay]

verified in 1/12 build.