ansaurus

Question

tinymce not working with chrome when i dynamically setcontent

Answer 1

A:

I had a similar problem (editor not showing in chrome) and read in some forum, that if tinyMCE is unable to locate some files, it just stops loading. Try tracking down if everything is found using firebug's net tab (clear your cache first).

stefita 2009-09-03 09:29:09

Answer 2

+2 A:

First of all; see to it that you have the latest version of TinyMCE.

I could not reproduce your problem given the information you provides. It seems just fine ( with the faked ajaxload ).

You could always try to go the "back entrance" in;

var myed = document.getElementById('elm1_ifr');
myed.contentDocument.getElementById('tinymce').innerHTML="<p style=\"text-align: center;\"><strong>hacking <span style=\"font-size: small;\">my</span> way in.</strong></p>";

Hope you good luck!

Frank 2009-09-05 08:02:24

Answer 3

+8 A:

Background:

For various reasons onload() is not considered the proper approach for loading Javascript, see for example Launching Code on Document Ready, with the most important/noticeable one being that Javascript code isn't run until the page has finished downloading entirely, including images and the like, which might take an eternity therefore (e.g. if an external banner ad server is down etc.).

Instead it is recommended to load Javascript as soon as the DOM is ready, but unfortunately there is no cross browser compatible native solution for this, see Getting notified when the page DOM has loaded (but before window.onload); please note that my entire answer is based upon the most excellent Javascript library jQuery, which offers a cross browser solution for this problem, consequently I'd definitely favor the two higher voted answers over the accepted solution myself.

Likely cause:

Your issue seems to be caused by the opposite behavior though: Chrome facilitates the WebKit rendering engine, just like Safari, and for the latter onload() is discussed to behave differently, see section When does onload fire? in Is Safari faster?. Another description of this problem specific to Chrome can be found in window.onload not working correctly in Chrome, without an explanation though.

In conclusion I suspect onload() to fire before the DOM is actually loaded completely, at least concerning the requirements of TinyMCE, which is notoriously fragile regarding issues like this and simply ceases to load.

Possible solution:

Just facilitating attribute defer on the script tag as outlined in window.onload not working correctly in Chrome is again not cross browser compatible, hence I'd simply go with the widely deployed and proven approach of using the already mentioned jQuery cross browser solution for the onload() problem, which is good practice anyway and should in principle take care of your inverse issue as well.

Update:

There are indeed some bugs filed against WebKit which could back my conclusion (no matter whether this behavior actually constitutes a bug or is intentional), see:

Steffen Opel 2009-09-09 01:13:55

Answer 4

+1 A:

same problem here, ie needs

var ed = tinyMCE.get('content');
ed.setContent('zzz');

other browsers

document.getElementById("content").innerHTML="zzz";

i am quite disapointed

will need to check browser in javascript to get it working properly, thats suxx

kvizmajster 2010-03-22 18:06:12

Answer 5

A:

There are a few ways to set content in a TinyMCE editor. If you want the content to be there when the page first loads, you can just put it between the tags.

Otherwise, you can do this through script in the following way:

window.onload = function() {

tinyMCE.getInstanceById("ProfileText").setContent('test');

};

I have wrapped the code in a window.onload block. If you have other functions that set content dynamically through this way after the TinyMCE editor has already loaded, then you do not need that.

Abu Arqam 2010-03-23 06:19:49

ansaurus

tags:

views:

answers:

tinymce not working with chrome when i dynamically setcontent

related questions