InlineEditBox: editor="dijit.Editor" doesn't work

[guest]

Browser: Firefox 2.0.0.9
Dojo Version: 1.0 (installed locally)
Error: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDOMNSHTMLDocument.designMode]

That error does not occur with other types of editors. I can use the dijit.Editor outside of the InlineEditBox? without problems. A short note on the InlineEditBox?-Site in the doc suggest it should work. I searched the site and googled for a while but found no solution, let alone mention of that problem.

That's how I did it (produces the error every time on my system):

<p dojoType="dijit.InlineEditBox" editor="dijit.Editor">
    edit me
</p>

It doesn't matter if I add renderAsHtml="true" or anything.

[bill]

FYI, I started to look at this one, but it might be a bit difficult to fix. Programmatic Editor creation does work (see [11801]), but as you said InlineEditBox? fails. For one thing, Editor doesn't have a focusNode attribute, so we crash there. I also think the FF2 iframe though will be problematic, especially w.r.t. copying over the source node's style to the editor.

[bill]

(In [11802]) Test case for InlineEditBox? on dijit.Editor, which doesn't work yet. Refs #5081.

[guest]

Just FYI, it works nice and without errors on Safari 3 (rendering with webkit).

[doughays]

IBM #83982

[doughays]

Editor patch to support InlineEditBox?

[doughays]

The patch needs to be reviewed for regressions. I added a focusNode to RichText?.js and changed the InlineEditBox? template to use a DIV instead of INPUT tag as the srcNodeRef default element. I changed the test to be autosave since Editor does not (yet?) support intermediate onChange notifications and thus the Save button in InlineEditBox? won't enable until a blur event is received in RichText?. This function would be handled by #5891.

[doughays]

(In [14283]) Fixes #5081. Added focusNode to RichText? editor and changed the InlineEditBox? widget template to use a div instead of an input tag. Changed the inline test to be autosave=true since Editor currently only fires onChange events after a blur.

[doughays]

(In [14376]) References #5081. Add support for InlineEditBox? to use Editor in !autoSave mode.

[doughays]

(In [15141]) References #5081, #7549. Readd focusNode to Editor for InlineEditBox? to use.

[bill]

This isn't working on IE, see #7613.

[bill]

(In [15175]) Since the Editor may output <p> tags, and nested <p> tags are illegal, declare the InlineEditBox? with a <div>.

This makes IE sort-of work although the font looks terrible because the 75% is applied multiple times so it's really small. (Copying the font-size as a computed-style isn't working well; it copies "75% "rather than "12pt".)

Refs #5081

[doughays]

(In [15177]) Fixes #5081. Added specific font-size to the Editor test so IE doesn't apply the relative size over and over. Changed Editor to apply user font styling to the iframe body style.

[bill]

FYI, turns out the font size problem is unrelated to InlineEditBox and is a regression from [14525], see #7636 and original ticket #6755.

[bill]

(In [15230]) remove workaround code added in [15177], not needed after [15229]. refs #5081