I noticed two things in the javascript that's doing the heavy lifting...
1) In the code below, the value of the text area must be set with 'val' rather than 'html'...or around half of the time you'd get an empty (but functioning) editor. 2) If the editor is created before the dialog is open, you'd get the behaviour observed in the original post. If the dialog is opened, and then the editor is created, it seems to be happy in Chrome (though I still am getting the error in the console about "<head> must be a child of <html>"...strange).
$('.edittable').click(function(){
// Copy the contents of the section.
edtarget=$(this);
edtype = $(this).attr("class");
edid = $(this).attr("id");
// have to use val instead of html here to make chrome happy.
$('#dialog').val($(this).html());
// this must come before the ckeditor() below.
eddialog.dialog("open");
$('#dialog').ckeditor();
});
Re: [SOLVED with voodoo]Bug in Chrome?
1) In the code below, the value of the text area must be set with 'val' rather than 'html'...or around half of the time you'd get an empty (but functioning) editor.
2) If the editor is created before the dialog is open, you'd get the behaviour observed in the original post. If the dialog is opened, and then the editor is created, it seems to be happy in Chrome (though I still am getting the error in the console about "<head> must be a child of <html>"...strange).
$('.edittable').click(function(){ // Copy the contents of the section. edtarget=$(this); edtype = $(this).attr("class"); edid = $(this).attr("id"); // have to use val instead of html here to make chrome happy. $('#dialog').val($(this).html()); // this must come before the ckeditor() below. eddialog.dialog("open"); $('#dialog').ckeditor(); });