Hello All,
I'm running into an error message on webkit-based browsers (both safari and chrome under windows)I hope someone can help with.
This is a pared down sample page:
http://docrobot.co.uk/static/test.html
When you click on a grey box, a dialogue appears with a CKeditor inside, along with the text of the box. You edit the box. Click save. The text is copied back into the original div, and then ajaxed up to the server.
My development machine is Windows XP SP3 (recently fully patched), Core 2 Duo E6600, 2GB RAM.
Using FF 3.6/IE 8.0.6001.whatever the dialogue works perfectly, the text shows up quickly, allows for editing, and then goes away.
Using Chrome 4.1.249 or Safari 4.0, the behaviour is that the dialogue box appears once as intended, and can be dismissed. Thereafter, though, when the block is clicked on, the dialogue appears, the editor appears, but no editing frame. The java console has an error "<head> must be a child of <html>. Content ignored." Nothing can be done with this window except to close it (the cancel or save buttons will still close it).
Opera 10.0 (though I'm not terribly concerned about this) has more erratic behaviour. The first time a box is clicked, the dialogue shows up as intended. The second time, it apparently has the same sort of behaviour as the webkit browsers. The third time, however, the toolbars don't show up at all, but the text does appear in a very small text area (presumably the text area of the dialog) so I'm guessing a catastrophic failure of ckeditor there. The buttons at the bottom of the dialougue are hosed enough that the only way to close the dialogue is the 'x' in the upper Like I said, not a priority for me.
I've searched for various things in the forum but can't find anything directly related that I can tell.
Can anyone else see where I went wrong? I expect I'm doing something silly, but I can't see what.
-Ken
Mon, 03/22/2010 - 08:17
#1
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).