Opened 10 years ago

Closed 10 years ago

#9463 closed defect (fixed)

Editor: programmatic creation / value parameter doesn't work

Reported by: bill Owned by: Jared Jurkiewicz
Priority: high Milestone: 1.5
Component: Editor Version: 1.3.0
Keywords: Cc:
Blocked By: Blocking:

Description

Although

myEditor.attr('value', ...)

works fine,

new dijit.Editor({value: ...}, srcNodeRef)

doesn't.

Editor always tries to read the initial value from the srcNodeRef, even if a value parameter was specified. The code for this is tangled up in open(), the same method that creates the iframe. Ironically, open() ends up with a string called "html" and uses that to set the editor's value, so the capability to set the initial value from a string is there.

Should probably move the code to snarf the initial editor value (as a string) from srcNodeRef into postMixInProperties(), and only run it if a value parameter hasn't been specified.

Attachments (1)

ProgCreationInitialValue.patch (3.0 KB) - added by Jared Jurkiewicz 10 years ago.
Quick patch that provides this function

Download all attachments as: .zip

Change History (5)

comment:1 Changed 10 years ago by bill

PS: workaround is to set srcNodeRef.innerHTML to value.

comment:2 Changed 10 years ago by bill

Milestone: 1.4future

Changed 10 years ago by Jared Jurkiewicz

Quick patch that provides this function

comment:3 Changed 10 years ago by Jared Jurkiewicz

Milestone: future1.5
Owner: changed from bill to Jared Jurkiewicz

comment:4 Changed 10 years ago by Jared Jurkiewicz

Resolution: fixed
Status: newclosed

(In [22048]) Small fix to allow programmatic setting of initial editor content. \!strict fixes #9463

Note: See TracTickets for help on using tickets.